netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit PAPILLAULT <benoit.papillault@free.fr>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net
Subject: ip_rt_min_delay : why 2s by default?
Date: Fri, 30 May 2008 12:37:06 +0200	[thread overview]
Message-ID: <483FD8D2.1030604@free.fr> (raw)

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


                 reply	other threads:[~2008-05-30 10:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=483FD8D2.1030604@free.fr \
    --to=benoit.papillault@free.fr \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).