From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, willemb@google.com, kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH net-next] ipv4: raise IP_MAX_MTU to theoretical limit
Date: Tue, 20 Aug 2013 15:08:23 -0700 (PDT) [thread overview]
Message-ID: <20130820.150823.291614792734267659.davem@davemloft.net> (raw)
In-Reply-To: <1376878087.4226.41.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Sun, 18 Aug 2013 19:08:07 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> As discussed last year [1], there is no compelling reason
> to limit IPv4 MTU to 0xFFF0, while real limit is 0xFFFF
>
> [1] : http://marc.info/?l=linux-netdev&m=135607247609434&w=2
>
> Willem raised this issue again because some of our internal
> regression tests broke after lo mtu being set to 65536.
>
> IP_MTU reports 0xFFF0, and the test attempts to send a RAW datagram of
> mtu + 1 bytes, expecting the send() to fail, but it does not.
>
> Alexey raised interesting points about TCP MSS, that should be addressed
> in follow-up patches in TCP stack if needed, as someone could also set
> an odd mtu anyway.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied, thanks for following through on this Eric.
prev parent reply other threads:[~2013-08-20 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 2:08 [PATCH net-next] ipv4: raise IP_MAX_MTU to theoretical limit Eric Dumazet
2013-08-20 22:08 ` David Miller [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=20130820.150823.291614792734267659.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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