Searched hist:ccd0628fca440268711560a1dbacc727b4f9e214 (Results 1 – 1 of 1) sorted by relevance
/linux/net/ipv4/ |
H A D | tcp_input.c | diff ccd0628fca440268711560a1dbacc727b4f9e214 Thu Apr 30 19:35:42 CEST 2020 Eric Dumazet <edumazet@google.com> tcp: tcp_sack_new_ofo_skb() should be more conservative
Currently, tcp_sack_new_ofo_skb() sends an ack if prior acks were 'compressed', if room has to be made in tp->selective_acks[]
But there is no guarantee all four sack ranges can be included in SACK option. As a matter of fact, when TCP timestamps option is used, only three SACK ranges can be included.
Lets assume only two ranges can be included, and force the ack:
- When we touch more than 2 ranges in the reordering done if tcp_sack_extend() could be done.
- If we have at least 2 ranges when adding a new one.
This enforces that before a range is in third or fourth position, at least one ACK packet included it in first/second position.
Signed-off-by: Eric Dumazet <edumazet@google.com> Acked-by: Soheil Hassas Yeganeh <soheil@google.com> Acked-by: Neal Cardwell <ncardwell@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|