Page MenuHomeFreeBSD

tcp: update "cubic_k" with the new formula from RFC8312bis.
Needs RevisionPublic

Authored by rscheff on Aug 31 2023, 9:29 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Dec 9, 5:53 PM
Unknown Object (File)
Nov 21 2024, 9:39 PM
Unknown Object (File)
Nov 8 2024, 4:17 AM
Unknown Object (File)
Nov 7 2024, 11:31 PM
Unknown Object (File)
Nov 7 2024, 10:47 PM
Unknown Object (File)
Oct 29 2024, 2:14 AM
Unknown Object (File)
Oct 29 2024, 2:06 AM
Unknown Object (File)
Oct 2 2024, 10:18 PM
Subscribers

Details

Reviewers
cc
tuexen
jtl
rrs
glebius
lstewart
Group Reviewers
transport
Summary

2nd patch in series to update Cubic in conformation with RFC8312bis.

This updates the calculation of K using the formula from this RFC document.

The new formula additionally uses "cwnd_epoch" for calculating K.

(1st in series: D40436)

This Diff is sliced from a summary patch provided by VMware to improve short RTT performance of Cubic.
Once all patches have been prepared and reviewed, they will go in together to make an atomic change
to cubic from pre-RFC status, to 8312bis status.

Test Plan

Submitted By: Bhaskar Pardeshi, VMware Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 53369
Build 50260: arc lint + arc unit

Event Timeline

cc requested changes to this revision.Sep 1 2023, 9:39 PM
cc added inline comments.
sys/netinet/cc/cc_cubic.c
334

Here, we are mixing the usage of "CUBICFLAG_CONG_EVENT" flag with the usage of "num_cong_events" variable below in the cases of cubic_cong_signal().

We shall not use both. Suggest remove the usage of "num_cong_events" as in commit 6907bbae187e

This revision now requires changes to proceed.Sep 1 2023, 9:39 PM
sys/netinet/cc/cc_cubic.c
334

Yes; I'm not done yet in dissecting the summary patch into smaller snippets; the flags will all be removed and only the num_cong_events remaining...

If you think it is unneccessary to split up the patch into logical subunits - which compile but may contain logic shortcomings, I can simply discard these (currently 2, probably will be 6-9) diffs and provide a single summary Diff?

sys/netinet/cc/cc_cubic.c
334

Reading probably 6 to 9 patches and looking up connecting logics may also be a challenge. Also test the single patch by emulation is easier. I prefer to a single patch on top of the 1st patch which is committed as eb5bfdd06565.

Others thoughts?