Grave neigh_periodic_timer bug?

[Arjan van de Ven]

Alexey Kuznetsov wrote:
> And even more if hash table is large enough.
> 
> Obviously, it should scan more than one hash bucket per tick to keep
> timer frequency reasonable. The question is what is reasonable?
> 

there are two possible answers for this ;)

1) For really low power syatems, "once every 30 seconds" is nice :0
   But to be realistic, if you use round_jiffies(), it won't be all 
that bad

or answer 2

2) use deferrable timers. These are like normal timers, but don't 
happen when the system is totally idle, but just instead fire when you 
get out of idle (say, when a network interrupt happens). This could be 
the best of both worlds in this case; if there's no network traffic or 
any other activity, the timer doesn't happen, but if there's activity 
it'll happen as usual