From: Eric Dumazet <erdnetdev@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [RFC] IP_MAX_MTU value
Date: Fri, 21 Dec 2012 10:34:39 -0800 [thread overview]
Message-ID: <1356114879.21834.7709.camel@edumazet-glaptop> (raw)
In-Reply-To: <50D4A84D.1010402@hp.com>
On Fri, 2012-12-21 at 10:19 -0800, Rick Jones wrote:
> If you go beyond the protocol limit of an IPv4 datagram, won't it be
> necessary to start being a bit more conditional on IPv4 vs IPv6?
>
This IP_MAX_MTU is really an IPv4 thing (static to net/ipv4/route.c)
>
> 99 times out of 10 I will assert that faster is better, but do we need
> another 50% for UDP over loopback with that large a message size?
Well, I only didnt understand why sending 65507 UDP messages had to use
fragments. I didnt care of performance at this point, only tried to have
an reasonable explanation.
It turns out its a strange limitation.
next prev parent reply other threads:[~2012-12-21 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 6:47 [RFC] IP_MAX_MTU value Eric Dumazet
2012-12-21 7:08 ` Eric Dumazet
2012-12-21 18:19 ` Rick Jones
2012-12-21 18:34 ` Eric Dumazet [this message]
2012-12-21 18:50 ` Rick Jones
2012-12-21 18:54 ` Eric Dumazet
2012-12-21 19:59 ` David Miller
2012-12-21 23:45 ` Alexey Kuznetsov
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=1356114879.21834.7709.camel@edumazet-glaptop \
--to=erdnetdev@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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