public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Simeon Penev <spenev@istac.de>
Cc: netdev@vger.kernel.org
Subject: Re: Patch for MTU in the routing table cache
Date: Fri, 02 Mar 2012 06:27:16 -0800	[thread overview]
Message-ID: <1330698436.2469.27.camel@edumazet-laptop> (raw)
In-Reply-To: <4F50CFE1.5040605@istac.de>

Le vendredi 02 mars 2012 à 14:49 +0100, Simeon Penev a écrit :
> Hi Eric,
> 
> no, i didn't. I'm new to the developer list and just wanted to post a 
> patch proposition. I hoped that the maintainer of the code (probably 
> Alan Cox) will decide whether to use it.
> 

David Miller is the current network maintainer, but thats not the
point :)

I didnt test your patch, all I wanted to say is that you cant assume all
routes share the same MTU (device MTU)

And this is the assumption you coded :

if (mtu && rt_is_output_route(rt) && mtu == dst->dev->mtu)
	return mtu;

      reply	other threads:[~2012-03-02 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 13:13 Patch for MTU in the routing table cache Simeon Penev
2012-03-02 13:43 ` Eric Dumazet
2012-03-02 13:49   ` Simeon Penev
2012-03-02 14:27     ` Eric Dumazet [this message]

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=1330698436.2469.27.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=spenev@istac.de \
    /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