RFC TCP congestion control RTT patches
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | TCP: congestion control API pass RTT in microsecondsinclude/ net/ net/ +9 more | +39 | 0 replies | |
| 2/3 | TCP: cubic - eliminate use of receive time stampnet/ | +18 | 1 reply | |
| 3/3 | TCP: htcp - use measured rttnet/ | +4 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/3] TCP congestion control RTT patches
These patches deal with issues brought up by Gavin McCullagh about reactions of Cubic and HTCP to hostile receivers that return bogus timestamp options. In a couple of places the timestamp value is used in ways that could cause unfairness.
The solution in these patches is to only use local values to measure RTT for congestion control. The timestamp is still used as described in RFC's to measure RTT used for retransmit timer.
This code is preliminary and not throughly tested yet. It could be backported to 2.6.22 for stable kernels, but it would be hard to go back to earlier kernels because it builds on the recent TCP congestion control API changes.