diff options
| author |   Yuchung Cheng <ycheng@google.com> | 2017-01-12 22:11:38 -0800 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2017-01-13 22:37:16 -0500 |
| commit | 840a3cbe89694fad75578856976f180e852e69aa (patch) | |
| tree | f5b99c39985394312b5662604e2476eb795dd27b /net/ipv4/tcp_timer.c | |
| parent | tcp: extend F-RTO to catch more spurious timeouts (diff) | |
| download | linux-dev-840a3cbe89694fad75578856976f180e852e69aa.tar.xz linux-dev-840a3cbe89694fad75578856976f180e852e69aa.zip | |
tcp: remove forward retransmit feature
Forward retransmit is an esoteric feature in RFC3517 (condition(3)
in the NextSeg()). Basically if a packet is not considered lost by
the current criteria (# of dupacks etc), but the congestion window
has room for more packets, then retransmit this packet.
However it actually conflicts with the rest of recovery design. For
example, when reordering is detected we want to be conservative
in retransmitting packets but forward-retransmit feature would
break that to force more retransmission. Also the implementation is
fairly complicated inside the retransmission logic inducing extra
iterations in the write queue. With RACK losses are being detected
timely and this heuristic is no longer necessary. There this patch
removes the feature.
Signed-off-by: Yuchung Cheng <ycheng@google.com>
Signed-off-by: Neal Cardwell <ncardwell@google.com>
Acked-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions