> due to conflicting models The big one is this, and this will wreck a lot of pre-io_uring APIs: Historically, you pass in a buffer to read(2). There is one b

> due to conflicting models The big one is this, and this will wreck a lot of pre-io_uring APIs: Historically, you pass in a buffer to read(2). There is one buffer per pending read. (And this is a scalability limitation.) With io_uring, you have a pool of buffers and a read completes by grabbing a buffer from the pool and putting the data there. io_uring highest-performance API is fundamentally at odds with the historical read API that was inherited from POSIX to just about every stdlib.