| 5e248c23 | 24-Feb-2024 |
Richard Scheffenegger <rscheff@FreeBSD.org> |
tcp: retain some CC signals outside of kernel scope
Summary: fix build error after f74352fbcf15341accaf5a92240871f98323215d
Reviewers: #transport!
Subscribers: imp, melifaro, glebius
Differential
tcp: retain some CC signals outside of kernel scope
Summary: fix build error after f74352fbcf15341accaf5a92240871f98323215d
Reviewers: #transport!
Subscribers: imp, melifaro, glebius
Differential Revision: https://reviews.freebsd.org/D44066
show more ...
|
| 038699a8 | 24-Feb-2024 |
Richard Scheffenegger <rscheff@FreeBSD.org> |
tcp: cubic - restart epoch after RTO
This is a migitation to avoid sudden extreme jumps in
cwnd, as t_epoch can be very out of date after an RTO.
Per RFC9438, sec 4.8, t_epoch is to be reset wheneve
tcp: cubic - restart epoch after RTO
This is a migitation to avoid sudden extreme jumps in
cwnd, as t_epoch can be very out of date after an RTO.
Per RFC9438, sec 4.8, t_epoch is to be reset whenever
cwnd grows beyond ssthresh (CC phase transitions from
slow start to congestion avoidance), to be fixed with
the upcoming cc_cubic changes.
MFC after: 3 days
Reviewed By: cc, #transport
Sponsored by: NetApp, Inc
Differential Revision: https://reviews.freebsd.org/D44023
show more ...
|
| f74352fb | 24-Feb-2024 |
Richard Scheffenegger <rscheff@FreeBSD.org> |
tcp: use enum for all congestion control signals
Facilitate easier troubleshooting by enumerating
all congestion control signals. Typecast the
enum to int, when a congestion control module uses
priv
tcp: use enum for all congestion control signals
Facilitate easier troubleshooting by enumerating
all congestion control signals. Typecast the
enum to int, when a congestion control module uses
private signals.
No external change.
Reviewed By: glebius, tuexen, #transport
Sponsored by: NetApp, Inc.
Differential Revision: https://reviews.freebsd.org/D43838
show more ...
|
| 32a6df57 | 08-Feb-2024 |
Richard Scheffenegger <rscheff@FreeBSD.org> |
tcp: calculate ssthresh on RTO according to RFC5681
per RFC5681, only adjust ssthresh on the initital
retransmission timeout. Since RTO often happens
during loss recovery, while cwnd no longer track
tcp: calculate ssthresh on RTO according to RFC5681
per RFC5681, only adjust ssthresh on the initital
retransmission timeout. Since RTO often happens
during loss recovery, while cwnd no longer tracks
all data in flight, calculcate pipe properly.
Reviewed By: tuexen, #transport
Sponsored by: NetApp, Inc.
Differential Revision: https://reviews.freebsd.org/D43768
show more ...
|