Place to read io_uring design?

Place to read io_uring design?

[Levo D]

I read the man pages. I have a good idea of how to use the API but I can't understand why the API is the way it is. I have a handful of complaints, but I would rather learn more about the design so the API may make more sense to me. I'm specifically talking about the kernel api (I used it through syscalls,) not the c wrapper. Is there a document or something I can read?

Place to read io_uring design?

[Levo D]

I didn't see any pages about io uring design, could I ask questions about it here? I can start with simple. In the submission and completion offset struct, the mask (and flags) holds a 32bit index for us to get a 32bit value. Why not have it hold the value instead and remove offsets from the struct name? It makes me suspecious that the mask can change?

Another one is why have an offset table at all? Wouldn't it make everything more simple if there were a set of entry values we can pick from with a decaded struct for it? Wouldn't that make both user and kernel space more simple? I have no idea what value is most optimal for my usecase and picking one from a known list of values would have been nice. I see the man pages have been updated since I last read them so I'll be rereading them