netdev - Re: [net-next PATCH v2 5/9] mlx4: Add support for UDP tunnel segmentation with outer checksum offload

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: <CAJ3xEMj_Vez_pP0ZTVATR=AMNDF1fneZ3dVrfWT7NP1mj4APRQ@mail.gmail.com>
Date:	Mon, 2 May 2016 10:19:57 +0300
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	Alexander Duyck <alexander.duyck@...il.com>
Cc:	Alexander Duyck <aduyck@...antis.com>,
	"talal@...lanox.com" <talal@...lanox.com>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Michael Chan <michael.chan@...adcom.com>,
	David Miller <davem@...emloft.net>,
	Gal Pressman <galp@...lanox.com>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	Eran Ben Elisha <eranbe@...lanox.com>
Subject: Re: [net-next PATCH v2 5/9] mlx4: Add support for UDP tunnel
 segmentation with outer checksum offload

On Mon, May 2, 2016 at 5:25 AM, Alexander Duyck
<alexander.duyck@...il.com> wrote:
> On Sun, May 1, 2016 at 1:35 PM, Or Gerlitz <gerlitz.or@...il.com> wrote:
>> On Sat, Apr 30, 2016 at 1:43 AM, Alexander Duyck <aduyck@...antis.com> wrote:
>>> This patch assumes that the mlx4 hardware will ignore existing IPv4/v6
>>> header fields for length and checksum as well as the length and checksum
>>> fields for outer UDP headers.

>> I see now the above text appearing in bunch of similar commit of
>> yours, specifically to Intel drivers and mlx5... could you please
>> elaborate a bit more what you mean here and what are the practical
>> consequences of that characteristics?

>> I got that right NETIF_F_GSO_UDP_TUNNEL_CSUM means that the HW can do
>> segmentation for TCP packets encapsulated by UDP tunnel e.g VXLAN
>> where the outer checksum is not zero. AFAIK, any other outer checksum
>> value can't correctly be a constant... are you assuming here  RCO or
>> LCO?

> Actually it is really easy for outer UDP checksum to be constant as
> long as we keep the length of all segments constant.  This all ties
> back into LCO.  As long as the fields between the start of the UDP
> header and the start of the TCP header are either constant, as in the
> case of IPv6, or have their own checksum as in the case of IPv4 we
> will end up with the checksum of the outer header being constant.

cool. I would love seeing this documented somewhere, either in the
change log if you do a respin or on some kernel networking
documentation, is that part of the LCO documentation?

> So in effect as long as we can trust the hardware to segment every
> frame to the specified size and that it won't insert any extra data
> anywhere in that region that we aren't expecting we can guarantee that
> each frame will have the same checksum for the outer UDP header.

Wow, that is really cool, thanks for taking the time and explaining it over.

Just one more piece to clarify... in the general case (e.g inner
packet size 1.5k...64k), the last segment would not have the same
length as the other segments, what happens on that case?

Or.