Re: CONFIG_TCP_CONG_BBR not set on, in fc32 kernel confg

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 17, 2020 at 6:31 AM Joel Wirāmu Pauling <jwp@xxxxxxxxxx> wrote:

> 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.
>
> This is not something that has changed, git history
on  configs/fedora/generic/CONFIG_TCP_CONG_BBR show last change was the
general config reworking in 2017.  Even this did not change the way it was
set, only how our config files are generated.  Curious if something else
has changed in how userspace tries to load the modules.

Justin

On Tue, 17 Mar 2020 at 22:56, Peter Robinson <pbrobinson@xxxxxxxxx> 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@xxxxxxxxxx <jpauling@xxxxxxxxxx>
> _______________________________________________
> kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
>
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux