From: Levo D <l-asm@mail9fcb1a.bolinlang.com>
To: <io-uring@vger.kernel.org>
Subject: Place to read io_uring design?
Date: Fri, 27 Jun 2025 17:45:48 +0000 [thread overview]
Message-ID: <20250627174548.6C2B2FA82E@bolin> (raw)
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
next reply other threads:[~2025-06-27 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 17:45 Levo D [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-22 4:46 Place to read io_uring design? Levo D
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250627174548.6C2B2FA82E@bolin \
--to=l-asm@mail9fcb1a.bolinlang.com \
--cc=io-uring@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox