From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: [PATCH 0/2] unify registered buffer iovec imports
Date: Sat, 8 Mar 2025 18:21:14 +0000 [thread overview]
Message-ID: <cover.1741457480.git.asml.silence@gmail.com> (raw)
Extract a helper for some common chunks of registered buffer iovec
handling so that callers don't have to care about offsets.
Pavel Begunkov (2):
io_uring: introduce io_prep_reg_iovec()
io_uring: rely on io_prep_reg_vec for iovec placement
io_uring/net.c | 27 ++++-----------------------
io_uring/rsrc.c | 34 ++++++++++++++++++++++++++++++----
io_uring/rsrc.h | 5 +++--
io_uring/rw.c | 24 ++----------------------
4 files changed, 39 insertions(+), 51 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-08 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 18:21 Pavel Begunkov [this message]
2025-03-08 18:21 ` [PATCH 1/2] io_uring: introduce io_prep_reg_iovec() Pavel Begunkov
2025-03-08 18:21 ` [PATCH 2/2] io_uring: rely on io_prep_reg_vec for iovec placement Pavel Begunkov
2025-03-10 13:14 ` [PATCH 0/2] unify registered buffer iovec imports 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.1741457480.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