On Nov 16, 2023, at 17:50, Marek Zarychta <zarych...@plan-b.pwste.edu.pl> wrote:
W dniu 16.11.2023 o 10:13, tue...@freebsd.org pisze:
Dear all,
recently the main branch was changed to build the TCP RACK stack
which is a loadable kernel module, by default:
https://cgit.FreeBSD.org/src/commit/?id=3a338c534154164504005beb00a3c6feb03756cc
That's really good news and long-awaited change. Thank you.
As discussed on the bi-weekly transport call, it would be great if people
could test the RACK stack for their workload. Please report any problems to the
net@ mailing list or open an issue in the bug tracker and drop me a note via
email.
This includes regressions in CPU usage, regressions in performance or any other
unexpected change you observe.
You can load the kernel module using
kldload tcp_rack
You can make the RACK stack the default stack using
sysctl net.inet.tcp.functions_default=rack
Based on the feedback we get, the default stack might be switched to the
RACK stack.
Yes, please do it, at least for CURRENT. Last problem I have spotted with RACK
was fixed in June: it was missing support TCP-MD5:
https://cgit.freebsd.org/src/commit/?id=02b885b09d1e90574162a1442b9ede06cef2b13a
We switched to RACK since upgrading to early stable/13 and genuinely appreciate
this gift from Netflix. The performance improvement is invaluable, both in a
lossy LAN and on a long-haul overseas TCP connection.
Please let me know if you have any questions.
Are any MFCs planned, especially to stable/14 ? Now, when stable/14 is almost
in sync with main aka CURRENT it's an optimal time for such a MFC. When the
change hits stable/14, it would be possible to test it extensively and have it
fully functional in 14.1-RELEASE.
