On 2019/1/25 15:07, Greg KH wrote:
> On Fri, Jan 25, 2019 at 09:50:35AM +0800, maowenan wrote:
>>
>>
>> On 2019/1/25 1:58, Greg KH wrote:
>>> On Wed, Jan 23, 2019 at 10:19:40AM +0800, Mao Wenan wrote:
From: Peter Oskolkov
[ Upstream commit fa0f527358bd900ef92f925878ed6bfbd51305cc
On Fri, Jan 25, 2019 at 09:50:35AM +0800, maowenan wrote:
>
>
> On 2019/1/25 1:58, Greg KH wrote:
> > On Wed, Jan 23, 2019 at 10:19:40AM +0800, Mao Wenan wrote:
> >> From: Peter Oskolkov
> >>
> >> [ Upstream commit fa0f527358bd900ef92f925878ed6bfbd51305cc ]
> >
> > This commit is not in the 4.1
On 2019/1/25 1:58, Greg KH wrote:
> On Wed, Jan 23, 2019 at 10:19:40AM +0800, Mao Wenan wrote:
>> From: Peter Oskolkov
>>
>> [ Upstream commit fa0f527358bd900ef92f925878ed6bfbd51305cc ]
>
> This commit is not in the 4.14.y tree, any specific reason why not?
I found the commit 6b921536f1707a24
On Wed, Jan 23, 2019 at 10:19:40AM +0800, Mao Wenan wrote:
> From: Peter Oskolkov
>
> [ Upstream commit fa0f527358bd900ef92f925878ed6bfbd51305cc ]
This commit is not in the 4.14.y tree, any specific reason why not?
thanks,
greg k-h
From: Peter Oskolkov
[ Upstream commit fa0f527358bd900ef92f925878ed6bfbd51305cc ]
Similar to TCP OOO RX queue, it makes sense to use rb trees to store
IP fragments, so that OOO fragments are inserted faster.
Tested:
- a follow-up patch contains a rather comprehensive ip defrag
self-test (fun