It only takes a few thousand lines (easily less than 10k even with zero dependencies and no standard library) to implement QUIC.
Kernel management of transport protocols has zero actual benefit for latency or throughput given proper network stack design. Neither does hardware offload except for crypto offload. Claimed differences are just due to poor network stack design and poor protocol implementation.
There is no real reason QUIC couldn't be implemented in the kernel though.
How is that relevant? The user agent (browser) handles the transport.
That’s the problem. Browsers are billion dollar ventures and are operating systems unto themselves. So they like QUIC.
But you have to include giant libraries and kernel can’t see the traffic to better manage timing etc.
Those are non-issues.
It only takes a few thousand lines (easily less than 10k even with zero dependencies and no standard library) to implement QUIC.
Kernel management of transport protocols has zero actual benefit for latency or throughput given proper network stack design. Neither does hardware offload except for crypto offload. Claimed differences are just due to poor network stack design and poor protocol implementation.