Page MenuHomeFreeBSD

tcp_rack: allow the module to be loaded without TCP_BLACKBOX
ClosedPublic

Authored by tuexen on Apr 27 2023, 9:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 19, 6:14 AM
Unknown Object (File)
Fri, Nov 15, 5:24 PM
Unknown Object (File)
Oct 24 2024, 4:03 AM
Unknown Object (File)
Oct 18 2024, 8:45 AM
Unknown Object (File)
Oct 2 2024, 4:02 AM
Unknown Object (File)
Sep 26 2024, 1:30 PM
Unknown Object (File)
Sep 18 2024, 9:57 PM
Unknown Object (File)
Sep 16 2024, 11:34 PM

Details

Summary

This fixes the issue reported in PR 271091.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Should the man-page tcp_rack(4) be changed at the same time to mention TCP_BLACKBOX as an optional dependency (and what feature it unlocks in rack)?

Should the man-page tcp_rack(4) be changed at the same time to mention TCP_BLACKBOX as an optional dependency (and what feature it unlocks in rack)?

I think the way to go would be to add a man page for TCP Black Box Logging (BBLog). It allows logging events and packets for the FreeBSD base stack, the RACK and the BBR stack. Logging is most detailed for the RACK stack. Please note that TCP_BLACKBOX is enabled by default.

Adding a BBLog man-page has no relation to fixing the build problem.

This revision was not accepted when it landed; it landed in state Needs Review.May 6 2023, 9:05 AM
This revision was automatically updated to reflect the committed changes.