diff options
| author | Yuchung Cheng <[email protected]> | 2017-01-12 22:11:34 -0800 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2017-01-13 22:37:16 -0500 |
| commit | 1d0833df594390876647c54c2c88069d29059665 (patch) | |
| tree | abd620968abad8f56e132a108b5bf354eb0d3b54 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 57dde7f70de34d4251f291c9eac7ad920aaf56b2 (diff) | |
tcp: use sequence to break TS ties for RACK loss detection
The packets inside a jumbo skb (e.g., TSO) share the same skb
timestamp, even though they are sent sequentially on the wire. Since
RACK is based on time, it can not detect some packets inside the
same skb are lost. However, we can leverage the packet sequence
numbers as extended timestamps to detect losses. Therefore, when
RACK timestamp is identical to skb's timestamp (i.e., one of the
packets of the skb is acked or sacked), we use the sequence numbers
of the acked and unacked packets to break ties.
We can use the same sequence logic to advance RACK xmit time as
well to detect more losses and avoid timeout.
Signed-off-by: Yuchung Cheng <[email protected]>
Signed-off-by: Neal Cardwell <[email protected]>
Acked-by: Eric Dumazet <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions