* ip_rt_min_delay : why 2s by default?
@ 2008-05-30 10:37 Benoit PAPILLAULT
0 siblings, 0 replies; only message in thread
From: Benoit PAPILLAULT @ 2008-05-30 10:37 UTC (permalink / raw)
To: netdev; +Cc: davem
Hi there,
I'm doing work on a IP routing protocol designed for mobility. During
testing phase, I encounter some 2s delay when routing table are updated.
I compare the routing table (displayed by route -n) and the routing
cache (displayed by route -Cn) and there was always a delay of 2s to
propagate changes from the routing table to the routing cache. Hence,
packet loss occurs.
Digging into the kernel source (net/ipv4/route.c), I found the
ip_rt_min_delay variable which is indeed 2s. I changed it to 0 through
/proc/sys/net/ipv4/route/min_delay and it seems that all my problems are
gone.
Questions:
1/ Is it safe to put 0 in min_delay? I'd like to make sure that it will
not trigger some bugs or inconsistencies later.
2/ If it is safe, then why it's not the default value? Is there a reason
for 2s or is it simply a compromise that so far nobody cares about 2s delay?
Regards,
Benoit
PS: Test was done with a 2.6.21.6 kernel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-05-30 10:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-30 10:37 ip_rt_min_delay : why 2s by default? Benoit PAPILLAULT
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.