From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
David Miller <davem@davemloft.net>
Cc: Francois WELLENREITER <f.wellenreiter@gmail.com>,
netdev@vger.kernel.org,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH] ipv6: Limit mtu to 65572 bytes
Date: Fri, 11 Apr 2014 11:30:44 +0900 [thread overview]
Message-ID: <534753D4.6070600@linux-ipv6.org> (raw)
In-Reply-To: <1397180530.16584.69.camel@edumazet-glaptop2.roam.corp.google.com>
Eric Dumazet wrote:
> We must limit the IPv6 MTU to (65535 + 40) bytes in theory.
>
> In practice, its better to align to a multiple of 4 for optimal TCP
> performance.
It is a TCP issue. We should not limit the mtu to 65532+40.
I am for 65535+40. Otherwise, other protocol such as UDP cannot
use full mtu as before.
--yoshfuji
next prev parent reply other threads:[~2014-04-11 2:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 19:42 Does IPv6 support Jumbograms ? Francois WELLENREITER
2014-04-09 20:35 ` Hannes Frederic Sowa
2014-04-09 21:41 ` Eric Dumazet
2014-04-09 22:35 ` Hannes Frederic Sowa
2014-04-10 0:36 ` Eric Dumazet
2014-04-10 13:28 ` Hannes Frederic Sowa
2014-04-10 14:01 ` Eric Dumazet
2014-04-10 23:54 ` Hannes Frederic Sowa
2014-04-11 0:40 ` Eric Dumazet
2014-04-11 1:42 ` [PATCH] ipv6: Limit mtu to 65572 bytes Eric Dumazet
2014-04-11 1:58 ` Eric Dumazet
2014-04-11 2:30 ` YOSHIFUJI Hideaki [this message]
2014-04-11 2:57 ` Hannes Frederic Sowa
2014-04-11 3:14 ` Eric Dumazet
2014-04-11 8:40 ` David Laight
2014-04-11 8:34 ` David Laight
2014-04-11 3:20 ` Eric Dumazet
2014-04-11 3:26 ` YOSHIFUJI Hideaki
2014-04-11 3:30 ` YOSHIFUJI Hideaki
2014-04-11 3:30 ` David Miller
2014-04-11 4:20 ` Eric Dumazet
2014-04-11 4:23 ` [PATCH v3] ipv6: Limit mtu to 65575 bytes Eric Dumazet
2014-04-11 13:22 ` Hannes Frederic Sowa
2014-04-11 15:26 ` Eric Dumazet
2014-04-11 20:48 ` David Miller
2014-04-11 2:44 ` [PATCH] ipv6: Limit mtu to 65572 bytes Hannes Frederic Sowa
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=534753D4.6070600@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=f.wellenreiter@gmail.com \
--cc=hannes@stressinduktion.org \
--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).