Thanks ; I guess a decision was made to build it as a module vs included in
baseline at some point. I hadn't even thought of checking modules.
On Tue, 17 Mar 2020 at 22:56, Peter Robinson <pbrobinson(a)gmail.com> wrote:
> I noticed that the kernel builds on the branched fedora32
kernels do not
> have CONFIG_TCP_CONG_BBR set ; meaning no shiny.
The kernel module is built:
$ modinfo tcp_bbr
filename:
/lib/modules/5.6.0-0.rc5.git0.2.fc32.x86_64/kernel/net/ipv4/tcp_bbr.ko.xz
description: TCP BBR (Bottleneck Bandwidth and RTT)
> root@kuriiti network-scripts]# sysctl
> net.ipv4.tcp_available_congestion_control
> net.ipv4.tcp_available_congestion_control = reno cubic
If you manually load the module it's there:
# sysctl -a | grep tcp_available_congestion_control
net.ipv4.tcp_available_congestion_control = reno cubic
# modprobe tcp_bbr
# sysctl -a | grep tcp_available_congestion_control
net.ipv4.tcp_available_congestion_control = reno cubic bbr
I'm not sure the "official" way to use different congestion control
algorithms but I'm guessing it's something you can use NetworkManager
to specify and autoload them.
Peter
--
Joel Wirāmu Pauling
Senior Solutions Architect
Mobile: (+64) 223608671
Email: jwp(a)redhat.com <jpauling(a)redhat.com>