netdev - Re: [PATCH net-next] ipv6: RTAX_FEATURE_ALLFRAG causes inefficient TCP segment sizing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120425.143926.1031867921141711841.davem@davemloft.net>
Date:	Wed, 25 Apr 2012 14:39:26 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	tore@....no, maze@...gle.com, netdev@...r.kernel.org,
	therbert@...gle.com
Subject: Re: [PATCH net-next] ipv6: RTAX_FEATURE_ALLFRAG causes inefficient
 TCP segment sizing

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Wed, 25 Apr 2012 12:02:37 +0200

> On Wed, 2012-04-25 at 11:38 +0200, Eric Dumazet wrote:
> 
>> Hmm, but what if we change linux to choice a) instead of b) ?
>> 
>> That is, not cap mtu to minimum value 1280 (and not use anymore
>> RTAX_FEATURE_ALLFRAG) : dst_allfrag() would be always false.
>> 
>> In this case, do we still need to send the frag header ?
>> 
>> I ask this because some TSO6 implementations probably dont cope very
>> well with this added header (untested path)
>> 
> 
> So a patch against net-next would looks like :
> 
> (Incredible, we remove some code in linux ;) )

I wouldn't mind applying this :-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html