https://blog.cloudflare.com/cloudflares-gen-x-servers-for-an...
https://blog.cloudflare.com/tubular-fixing-the-socket-api-wi...
https://blog.cloudflare.com/cloudflares-gen-x-servers-for-an...
https://blog.cloudflare.com/tubular-fixing-the-socket-api-wi...
With shared source, the network card vendor can even repackage some of the types of acceleration you write for their other clients - and I bet they're already looking into acceleration of HTTP/3.
It's a win-win - because cloudflare gets massive compute savings, and the network card vendor knows they've built quite a high moat to buying someone else's hardware.
https://www.nvidia.com/en-us/networking/ethernet/connectx-6-...
Last time I benchmarked io_uring, it was good enough, but I was able to get measurably faster from syscalls and a well-crafted userspace thread pool for storage to NVMe.
(Note: the I/O thread pool I wrote came out noticably faster than fio, the benchmark tool, so don't assume fio results are the best possible.)
For that reason, I have a small application which can be configured for either io_uring or the thread pool, and the thread pool is preferred for performance.