Chances are you might have heard of io_uring. It first appeared in Linux 5.1, back in 2019, and was advertised as the new API for asynchronous I/O. Its goal was to be an alternative to the deemed-to-be-broken-beyond-repair AIO, the “old” asynchronous I/O API. Calling io_uring just an asynchronous I/O API doesn’t do it justice, though. Underneath the API calls, io_uring is a full-blown runtime for
![Missing Manuals - io_uring worker pool](https://cdn-ak-scissors.b.st-hatena.com/image/square/b6b7f925359f3f16e01b3b5b9fd72286051d78b3/height=288;version=1;width=512/http%3A%2F%2Fblog.cloudflare.com%2Fcontent%2Fimages%2F2022%2F02%2FMissing-Manuals---io_uring-worker-pool-OG-1.png)