From: Levo D <l-asm@mail9fcb1a.bolinlang.com>
To: <io-uring@vger.kernel.org>
Subject: Place to read io_uring design?
Date: Sun, 22 Jun 2025 04:46:38 +0000 [thread overview]
Message-ID: <20250622044638.A15A2FA301@bolin> (raw)
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?
next reply other threads:[~2025-06-22 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 4:46 Levo D [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-27 17:45 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=20250622044638.A15A2FA301@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