netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Felipe Massia Pereira <massia@ic.unicamp.br>
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: mtu_expires variable
Date: Sun, 18 May 2003 17:40:24 -0700	[thread overview]
Message-ID: <20030518174024.014cb734.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10305162243050.13822-100000@tigre.dcc.unicamp.br>

On Fri, 16 May 2003 23:16:03 -0300 (EST) Felipe Massia Pereira <massia@ic.unicamp.br> wrote:   [on LKML]

| Hello,
| 
| I've been searching for the exact meaning of this variable through
| Documentation and I've found just empty descriptions (to be filled in, in
| Advanced Linux Routing HOWTO, and nothing also in
| Documentation/networking/ip-sysctl.txt). I've tried also to read the
| kernel source code (net/ipv4/route.c) but I could not figure out what they
| mean.

What kernel version?
And this question would be better asked/answered on either
linux-net or netdev mailing lists, so I've replied to those.

It (ip_rt_mtu_expires variable) appears not to be used very much.

| I've came accross this var because we want to do some experiments in class
| with Path MTU discovery.  But it happens that MTU is recorded between
| experiments (and it's what we expect: that the stack does not do a PMTU
| every time). BTW where is the PMTU value kept? Is MTU value recorded for
| each destination or for each route?
| 
| So it would be nice if we could make the value found in a experiment to be
| forgotten by the kernel so the students could execute the ping several
| times. (ping -c 2 -m want ...) Is mtu_expires what we're looking for?

Maybe someone else can answer this...

| We tried to "echo 1 > /proc/sys/net/ipv4/route/mtu_expires" considering
| that it's expressed in seconds. The usual value is 600. But I've read that
| it's expressed in jiffies. Jiffies occur 100 times per sec on a PC, is it?
| So the value 600 on a PC means 6 seconds?

In 2.4.x there are 100 jiffies / second on a PC (x86 arch).
However, /proc/sys/net/ipv4/route/mtu_expires is hiding this HZ
conversion factor from us, so that the value is expressed in seconds
and not in jiffies, so 600 is 600 seconds = 10 minutes.

--
~Randy

       reply	other threads:[~2003-05-19  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.10.10305162243050.13822-100000@tigre.dcc.unicamp.br>
2003-05-19  0:40 ` Randy.Dunlap [this message]
2003-05-19  1:32   ` mtu_expires variable David S. Miller

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=20030518174024.014cb734.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-net@vger.kernel.org \
    --cc=massia@ic.unicamp.br \
    --cc=netdev@oss.sgi.com \
    /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).