netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	Francois WELLENREITER <f.wellenreiter@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: Limit mtu to 65572 bytes
Date: Fri, 11 Apr 2014 04:44:42 +0200	[thread overview]
Message-ID: <20140411024442.GL27255@order.stressinduktion.org> (raw)
In-Reply-To: <1397180530.16584.69.camel@edumazet-glaptop2.roam.corp.google.com>

On Thu, Apr 10, 2014 at 06:42:10PM -0700, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
> 
> Francois reported that setting big mtu on loopback device could prevent
> tcp sessions making progress.
> 
> We do not support (yet ?) IPv6 Jumbograms and cook corrupted packets.
> 
> 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.
> 
> Tested:
> 
> ifconfig lo mtu 70000
> netperf -H ::1
> 
> Before patch :
> 
> -> Throughput :   0.05 Mbits
> 
> After patch :
> 
> -> Throughput : 36624.24 Mbits
> 
> Reported-by: Francois WELLENREITER <f.wellenreiter@gmail.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>

Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>

Sorry about my wrong statement earlier in this thread, you're right.

Btw. this patch fixes a flaw in the UDP output path, too, where we didn't
generate EMSGSIZE error correctly before in all cases. udp_sendmsg only checks
for INT_MAX - sizeof(udphdr) and defers further checking to ip6_append_data
which seems to be prepared for jumbograms. ;)

Very cool catch with the possible ipv4 performance improvment, too. ;)

Thanks,

  Hannes

      parent reply	other threads:[~2014-04-11  2:44 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
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             ` Hannes Frederic Sowa [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=20140411024442.GL27255@order.stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=f.wellenreiter@gmail.com \
    --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).