Re: [PATCH net-next 2/4] tcp: do not force quickack when receiving out-of-order packets

2018-05-17 Thread Soheil Hassas Yeganeh
On Thu, May 17, 2018 at 8:12 AM, Eric Dumazet wrote: > As explained in commit 9f9843a751d0 ("tcp: properly handle stretch > acks in slow start"), TCP stacks have to consider how many packets > are acknowledged in one single ACK, because of GRO, but also > because of ACK compression or losses. > >

Re: [PATCH net-next 2/4] tcp: do not force quickack when receiving out-of-order packets

2018-05-17 Thread Neal Cardwell
On Thu, May 17, 2018 at 8:12 AM Eric Dumazet wrote: > As explained in commit 9f9843a751d0 ("tcp: properly handle stretch > acks in slow start"), TCP stacks have to consider how many packets > are acknowledged in one single ACK, because of GRO, but also > because of ACK compression or losses. > W

[PATCH net-next 2/4] tcp: do not force quickack when receiving out-of-order packets

2018-05-17 Thread Eric Dumazet
As explained in commit 9f9843a751d0 ("tcp: properly handle stretch acks in slow start"), TCP stacks have to consider how many packets are acknowledged in one single ACK, because of GRO, but also because of ACK compression or losses. We plan to add SACK compression in the following patch, we must t