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: <CAKgT0UcfzuEH7EzF9krziDQ1r_t3_LVTRNMvJxaQ60-HzypLyQ@mail.gmail.com>
Date:	Sun, 7 Feb 2016 04:13:53 -0600
From:	Alexander Duyck <alexander.duyck@...il.com>
To:	Tom Herbert <tom@...bertland.com>
Cc:	Alexander Duyck <aduyck@...antis.com>,
	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	Edward Cree <ecree@...arflare.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [net-next PATCH 03/10] net: Update remote checksum segmentation
 to support use of GSO checksum

On Sat, Feb 6, 2016 at 2:44 PM, Tom Herbert <tom@...bertland.com> wrote:
> On Fri, Feb 5, 2016 at 3:27 PM, Alexander Duyck <aduyck@...antis.com> wrote:
>> This patch addresses two main issues.
>>
>> First in the case of remote checksum offload we were avoiding dealing with
>> scatter-gather issues.  As a result it would be possible to assemble a
>> series of frames that used frags instead of being linearized as they should
>> have if remote checksum offload was enabled.
>>
>> Second I have updated the code so that we now let GSO take care of doing
>> the checksum on the data itself and drop the special case that was added
>> for remote checksum offload.
>>
> Did you test this (with vxlan or GUE)?

I was testing with VXLAN.

- Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ