"DualPI2 and TCP-PRague are currently being mainlined to kernel 6.12!" doesn't seem accurate

[jkasten2]

The public page https://l4steam.github.io/ states:

DualPI2 and TCP-PRague are currently being mainlined to kernel 6.12!

However, I see no mention of DualPI2 in the Linux Kernel source.
https://github.com/search?q=repo%3Atorvalds%2Flinux+DualPI2&type=code

This issue also says that other parts like tcp_prague_info haven't been mainlined yet either.

• Also not seeing prague_enabled in the Linux Kernel either.

@koen0607 @bbriscoe

[koen0607]

It was accurate for the part that we are upstreaming it since the 6.12 release (check the net-next mailing list for status). In the mean time we missed this release with mainly the Accurate ECN feature being the bottleneck issue. Accurate ECN is a mandatory feature for TCP-Prague and seems to have quite some interworking issues with acceleration HW and SW. We are working on this as much as we can to get this through. For DualPI2 we also had some performance concerns about acceleration in data centers, but DualPI2 is not necessarily targetting high performance high speed DC bottlenecks and NICs, rather access and home devices and links. So also there some further discussions and convincing are required. For UDP, L4S can be deployed today in apps that want to use UDP-Prague. This makes most sense anyway to develop interactive apps with UDP (including UDP/QUIC).
We'll update the page to clarify the upstreaming status.