From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: [PATCH 0/7] further ring init cleanups
Date: Wed, 12 Nov 2025 12:45:52 +0000 [thread overview]
Message-ID: <cover.1762947814.git.asml.silence@gmail.com> (raw)
There are several goals for this patch set. It deduplicates ring size and
offset calculations between ring setup and resizing. It moves most of
verification earlier before any allocations, which usually means simpler
error handling. And it keeps the logic localised instead of spreading it
across the file.
Pavel Begunkov (7):
io_uring: refactor rings_size nosqarray handling
io_uring: use size_add helpers for ring offsets
io_uring: convert params to pointer in ring reisze
io_uring: introduce struct io_ctx_config
io_uring: keep ring laoyut in a structure
io_uring: pre-calculate scq layout
io_uring: move cq/sq user offset init around
io_uring/io_uring.c | 137 ++++++++++++++++++++++++--------------------
io_uring/io_uring.h | 19 +++++-
io_uring/register.c | 65 +++++++++------------
3 files changed, 119 insertions(+), 102 deletions(-)
--
2.49.0
next reply other threads:[~2025-11-12 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 12:45 Pavel Begunkov [this message]
2025-11-12 12:45 ` [PATCH 1/7] io_uring: refactor rings_size nosqarray handling Pavel Begunkov
2025-11-12 12:45 ` [PATCH 2/7] io_uring: use size_add helpers for ring offsets Pavel Begunkov
2025-11-12 12:45 ` [PATCH 3/7] io_uring: convert params to pointer in ring reisze Pavel Begunkov
2025-11-12 12:45 ` [PATCH 4/7] io_uring: introduce struct io_ctx_config Pavel Begunkov
2025-11-12 12:45 ` [PATCH 5/7] io_uring: keep ring laoyut in a structure Pavel Begunkov
2025-11-12 12:45 ` [PATCH 6/7] io_uring: pre-calculate scq layout Pavel Begunkov
2025-11-12 12:45 ` [PATCH 7/7] io_uring: move cq/sq user offset init around Pavel Begunkov
2025-11-12 19:33 ` [PATCH 0/7] further ring init cleanups Jens Axboe
2025-11-13 14:28 ` Jens Axboe
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=cover.1762947814.git.asml.silence@gmail.com \
--to=asml.silence@gmail.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