[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKgT0Ud-m1i0n1Dnbagpkii8jDYb-Wq43UQi+Dvv6b585jcJnQ@mail.gmail.com>
Date: Fri, 8 Apr 2016 15:12:22 -0700
From: Alexander Duyck <alexander.duyck@...il.com>
To: Jesse Gross <jesse@...nel.org>
Cc: Alexander Duyck <aduyck@...antis.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Tom Herbert <tom@...bertland.com>,
Eric Dumazet <edumazet@...gle.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>
Subject: Re: [net-next PATCH 2/5] GSO: Add GSO type for fixed IPv4 ID
On Fri, Apr 8, 2016 at 2:41 PM, Jesse Gross <jesse@...nel.org> wrote:
> On Fri, Apr 8, 2016 at 5:33 PM, Alexander Duyck <aduyck@...antis.com> wrote:
>> This patch adds support for TSO using IPv4 headers with a fixed IP ID
>> field. This is meant to allow us to do a lossless GRO in the case of TCP
>> flows that use a fixed IP ID such as those that convert IPv6 header to IPv4
>> headers.
>>
>> In addition I am adding a feature that for now I am referring to TSO with
>> IP ID mangling. Basically when this flag is enabled the device has the
>> option to either output the flow with incrementing IP IDs or with a fixed
>> IP ID regardless of what the original IP ID ordering was. This is useful
>> in cases where the DF bit is set and we do not care if the original IP ID
>> value is maintained.
>>
>> Signed-off-by: Alexander Duyck <aduyck@...antis.com>
>
> I think SKB_GSO_TCP_FIXEDID would also need to be added to the list of
> enumerated OK GSO types for MPLS GSO.
I'll have that fixed for v2.
- Alex
Powered by blists - more mailing lists