Denis Lunev f0098f7863 [NET] Fix too aggressive backoff in dst garbage collection ... The bug is evident when it is seen once. dst gc timer was backed off, when gc queue is not empty. But this means that timer quickly backs off, if at least one destination remains in use. Normally, the bug is invisible, because adding new dst entry to queue cancels the backoff. But it shots deadly with destination cache overflow when new destinations are not released for long time f.e. after an interface goes down. The fix is to cancel backoff when something was released. Signed-off-by: Denis Lunev <den@sw.ru> Signed-off-by: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru> Signed-off-by: David S. Miller <davem@davemloft.net>		2005-07-30 17:47:25 -07:00
..
datagram.c
dev_mcast.c
dev.c	[NET]: Fix busy waiting in dev_close().	2005-07-28 12:12:58 -07:00
dst.c	[NET] Fix too aggressive backoff in dst garbage collection	2005-07-30 17:47:25 -07:00
dv.c
ethtool.c
filter.c
flow.c
gen_estimator.c
gen_stats.c
iovec.c
link_watch.c
Makefile
neighbour.c
net-sysfs.c
netfilter.c
netpoll.c
pktgen.c
request_sock.c
rtnetlink.c
scm.c
skbuff.c
sock.c
stream.c
sysctl_net_core.c
utils.c
wireless.c