diff options
| author | Yuchung Cheng <[email protected]> | 2013-10-24 15:59:27 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2013-10-27 20:50:06 +0000 |
| commit | 2f715c1dde6e1760f3101358dc26f8c9489be0bf (patch) | |
| tree | b77474cc9f3e97000404dab09bde3429d62192ff /drivers/net/xen-netback/interface.c | |
| parent | tcp: only take RTT from timestamps if new data is acked (diff) | |
| download | kernel-2f715c1dde6e1760f3101358dc26f8c9489be0bf.tar.gz kernel-2f715c1dde6e1760f3101358dc26f8c9489be0bf.zip | |
tcp: do not rearm RTO when future data are sacked
Patch ed08495c3 "tcp: use RTT from SACK for RTO" always re-arms RTO upon
obtaining a RTT sample from newly sacked data.
But technically RTO should only be re-armed when the data sent before
the last (re)transmission of write queue head are (s)acked. Otherwise
the RTO may continue to extend during loss recovery on data sent
in the future.
Note that RTTs from ACK or timestamps do not have this problem, as the RTT
source must be from data sent before.
The new RTO re-arm policy is
1) Always re-arm RTO if SND.UNA is advanced
2) Re-arm RTO if sack RTT is available, provided the sacked data was
sent before the last time write_queue_head was sent.
Signed-off-by: Larry Brakmo <[email protected]>
Signed-off-by: Yuchung Cheng <[email protected]>
Acked-by: Neal Cardwell <[email protected]>
Acked-by: Eric Dumazet <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'drivers/net/xen-netback/interface.c')
0 files changed, 0 insertions, 0 deletions