TCP Prague Implementation for Kernel v6

[TillMueller]

I'd like to include TCP Prague as a candidate in a list of TCP optimizations I am working on performance comparisons for. My current testing setup is based on the somewhat recent kernel version 6.3, but haven't found a good way to get TCP Prague enabled for that kernel version.
Due to the way this repo is set up applying the commits on top of the Linux kernel in this repo doesn't really work. Is there an existing effort to get TCP Prague into kernel version 6?

Thank you in advance!

Till

[fernandodiacenco]

I'm also interested in this.

I'm trying my best to compile tcp-prague and dualpi2 on a NanoPi R5S to test it in real world conditions but I'm getting nowhere, Tried Stock Arm Debian 11 and Debian 12.

The only time it worked was when installing the .deb files on a virtual machine amd64 Debian 12, not even stock Debian 11 accepts the .deb files (It complains about zstd compression used in the .debs).

[minuscat]

I would like to share with you that the first v6 kernel is available: https://github.com/minuscat/l4steam-6.6.y
The pre-built kernel can be found: https://github.com/minuscat/l4steam-6.6.y/releases/download/testing-build/l4s-testing.zip
The kernel is patched on top of v6.6.40 LTS kernel now, and we will further move to newer v6.6.y kernel
At the meantime, we are also preparing v6.1.y kernel.

That branch will soon move back to L4STeam.

[warlock20]

I would like to share with you that the first v6 kernel is available: https://github.com/minuscat/l4steam-6.6.y The pre-built kernel can be found: https://github.com/minuscat/l4steam-6.6.y/releases/download/testing-build/l4s-testing.zip The kernel is patched on top of v6.6.40 LTS kernel now, and we will further move to newer v6.6.y kernel At the meantime, we are also preparing v6.1.y kernel.

That branch will soon move back to L4STeam.

Thanks for the new version.

One request. While moving the branch to the L4STeam, it would be great if you can publish the pre-built kernel version with eBPF support (i.e. enable BTF info during kernel build). Thank you

[aidanharris]

With recent changes to dualpi2 I'm seeing a compiler warning when building with modern versions of Gcc (14) and Clang (18). This warning becomes fatal when compiling with CONFIG_WERROR=y. I was able to silence it but I'm not sure what the correct fix is:

diff --git a/net/sched/sch_dualpi2.c b/net/sched/sch_dualpi2.c
index 69a26e3d22c0..3f19f122ad68 100644
--- a/net/sched/sch_dualpi2.c
+++ b/net/sched/sch_dualpi2.c
@@ -673,6 +673,11 @@ static const struct netlink_range_validation dualpi2_wc_range = {
 	.max = MAX_WC,
 };
 
+#ifndef CONFIG_CC_IS_CLANG
+#pragma GCC diagnostic ignored "-Wdiscarded-qualifiers"
+#else
+#pragma GCC diagnostic ignored "-Wincompatible-pointer-types-discards-qualifiers"
+#endif
 static const struct nla_policy dualpi2_policy[TCA_DUALPI2_MAX + 1] = {
 	[TCA_DUALPI2_LIMIT]		=
 		NLA_POLICY_FULL_RANGE(NLA_U32, &dualpi2_nonzero_range),

[minuscat]

@aidanharris This was because the const keyword there, and they are removed since my last push.
I verified this on a fresh compilation in Ubuntu 24.04, in where gcc14 is the default compiler.

linux/net/sched/sch_dualpi2.c

Lines 662 to 674 in d0e7371

	static struct netlink_range_validation dualpi2_nonzero_range = {
	.min = 1,
	};
	static struct netlink_range_validation dualpi2_alpha_beta_range = {
	.min = 1,
	.max = ALPHA_BETA_MAX,
	};
	static struct netlink_range_validation dualpi2_wc_range = {
	.min = 0,
	.max = MAX_WC,
	};

Note that this v6 branch will be constantly "rebased" to retain the same patches submitted for Linux upstreaming.
Therefore, please make sure to fetch/pull before local compilation, or you can get the pre-build in https://github.com/L4STeam/linux/releases/tag/l4steam-6.6.y-build

If the problem persists, please share the complete compilation message.