Re: [RFC PATCH 1/9] ipv4/GRO: Allow multiple frames to use the same IP ID

2016-03-27 Thread Jesse Gross
On Wed, Mar 23, 2016 at 7:21 PM, Alexander Duyck wrote: > On Wed, Mar 23, 2016 at 6:43 PM, Jesse Gross wrote: >> On Fri, Mar 18, 2016 at 4:24 PM, Alexander Duyck wrote: >>> In RFC 6864 it is stated that we can essentially ignore

Re: [RFC PATCH 1/9] ipv4/GRO: Allow multiple frames to use the same IP ID

2016-03-23 Thread Alexander Duyck
On Wed, Mar 23, 2016 at 6:43 PM, Jesse Gross wrote: > On Fri, Mar 18, 2016 at 4:24 PM, Alexander Duyck wrote: >> In RFC 6864 it is stated that we can essentially ignore the IPv4 ID field >> if we have not and will not use fragmentation. Such a frame is

Re: [RFC PATCH 1/9] ipv4/GRO: Allow multiple frames to use the same IP ID

2016-03-23 Thread Jesse Gross
On Fri, Mar 18, 2016 at 4:24 PM, Alexander Duyck wrote: > In RFC 6864 it is stated that we can essentially ignore the IPv4 ID field > if we have not and will not use fragmentation. Such a frame is defined > as having the DF flag set to 1, and the MF and frag_offset as 0.

[RFC PATCH 1/9] ipv4/GRO: Allow multiple frames to use the same IP ID

2016-03-18 Thread Alexander Duyck
In RFC 6864 it is stated that we can essentially ignore the IPv4 ID field if we have not and will not use fragmentation. Such a frame is defined as having the DF flag set to 1, and the MF and frag_offset as 0. Currently for GRO we were requiring that the inner header always have an increasing