8 May
2024
8 May
'24
2:32 p.m.
On Wed, May 8, 2024 at 12:36 AM Matthieu Baerts matttbe@kernel.org wrote:
The concern with picking reno is extra deps to CI and every developer. Currently in selftests/bpf/config we do: CONFIG_TCP_CONG_DCTCP=y CONFIG_TCP_CONG_BBR=y
I'd like to avoid adding reno there as well. Will bpf_setsockopt("dctcp") work?
We picked Reno because this is an inlined kernel module that is always built: there is no kernel config to set, no extra deps. Also, it is usually not used as default, mostly used as fallback, so the verification should not be an issue.
Ahh. didn't realize that it's builtin. Then sure. keep it as reno.