From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Francois WELLENREITER <f.wellenreiter@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Does IPv6 support Jumbograms ?
Date: Wed, 9 Apr 2014 22:35:15 +0200 [thread overview]
Message-ID: <20140409203515.GF27255@order.stressinduktion.org> (raw)
In-Reply-To: <5345A2B3.7040602@gmail.com>
Hi!
On Wed, Apr 09, 2014 at 09:42:43PM +0200, Francois WELLENREITER wrote:
> I've been recently running performance tests with the loopback interface
> increasing the MTU over the 65535 byte limit.
> I was really surprised to see that a simple scp onto the ::1 address
> systematically blocked after transferring about 2,4 MB.
> My interpretation of this behavior is that the current IPv6 kernel layer
> does not support Jumbograms at all. Am I wrong ?
> If that's not the case, what could then the right interpretation of this
> issue ?
> And whenever I'm right, is there any plan to support this feature in a
> near future ?
IPv6 should handle the reception of jumbo frames quite fine, even the UDP size
override IIRC. But there is no support for large outgoing UDP frames, and I
currently don't know about TCP-MSS override works.
I guess you should be able to send jumbos with rawsocket if you attach the
dsthop header manually, but I have never tried it (maybe it will get blocked
by some check in ip6_output, HDRINCL and H-b-H option setsockopt could work
also).
I currently don't see the need for that option if no one also takes care about
UDP and TCP paths, so I guess support is coming as soon as someone cares. ;)
Greetings,
Hannes
next prev parent reply other threads:[~2014-04-09 20:35 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 [this message]
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 ` [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=20140409203515.GF27255@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--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).