Re: [net-next 3/3] tcp: keep tcp_collapse controllable even after processing starts

2017-10-14 Thread Koichiro Den
On Sat, 2017-10-14 at 08:46 -0700, Eric Dumazet wrote: > On Sat, 2017-10-14 at 16:27 +0900, Koichiro Den wrote: > > Combining actual collapsing with reasoning for deciding the starting > > point, we can apply its logic in a consistent manner such that we can > > avoid costly yet not much useful

Re: [net-next 3/3] tcp: keep tcp_collapse controllable even after processing starts

2017-10-14 Thread Eric Dumazet
On Sat, 2017-10-14 at 16:27 +0900, Koichiro Den wrote: > Combining actual collapsing with reasoning for deciding the starting > point, we can apply its logic in a consistent manner such that we can > avoid costly yet not much useful collapsing. When collapsing to be > triggered, it's not rare that

[net-next 3/3] tcp: keep tcp_collapse controllable even after processing starts

2017-10-14 Thread Koichiro Den
Combining actual collapsing with reasoning for deciding the starting point, we can apply its logic in a consistent manner such that we can avoid costly yet not much useful collapsing. When collapsing to be triggered, it's not rare that most of the skbs in the receive or ooo queue are large ones