The UDP optimizations are already there and have been pretty much wrung out. https://www.fastly.com/blog/measuring-quic-vs-tcp-computational-efficiency/ https:

The UDP optimizations are already there and have been pretty much wrung out. https://www.fastly.com/blog/measuring-quic-vs-tcp-computational-efficiency/ https://www.fastly.com/blog/measuring-quic-vs-tcp-computatio... has good details and was done almost five years ago. The solution isn't in more UDP offload optimizations as there aren't any semantics in UDP that are expensive other than the quantity and frequency of datagrams to be processed in the context of the QUIC protocol that uses UDP as a transport. QUIC's state machine needs to see every UDP datagram carrying QUIC protocol messages in order to move forward. Just like was done for TCP offload more than twenty years ago, portions of QUIC state need to move and be maintained in hardware to prevent the host from having to see so many high-frequency tiny state updates messages.