From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: [PATCH 0/4] buffer table registration cleanup
Date: Fri, 4 Apr 2025 17:22:13 +0100 [thread overview]
Message-ID: <cover.1743783348.git.asml.silence@gmail.com> (raw)
Cleanup up buffer table registration, and deduplicate it with updates.
Similar series can be done for file tables.
Pavel Begunkov (4):
io_uring/rsrc: avoid assigning buf table on failure
io_uring: deduplicate node tagging
io_uring: early return for sparse buf table registration
io_uring: reuse buffer updates for registration
io_uring/rsrc.c | 111 ++++++++++++++++++------------------------------
1 file changed, 41 insertions(+), 70 deletions(-)
--
2.48.1
next reply other threads:[~2025-04-04 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 16:22 Pavel Begunkov [this message]
2025-04-04 16:22 ` [PATCH 1/4] io_uring/rsrc: avoid assigning buf table on failure Pavel Begunkov
2025-04-04 16:22 ` [PATCH 2/4] io_uring: deduplicate node tagging Pavel Begunkov
2025-04-04 16:22 ` [PATCH 3/4] io_uring: early return for sparse buf table registration Pavel Begunkov
2025-04-04 16:22 ` [PATCH 4/4] io_uring: reuse buffer updates for registration Pavel Begunkov
2025-04-04 16:38 ` Jens Axboe
2025-04-04 21:38 ` Pavel Begunkov
2025-04-04 22:00 ` 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.1743783348.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