From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: [PATCH 0/6] provided buffer cleanups
Date: Tue, 13 May 2025 18:26:45 +0100 [thread overview]
Message-ID: <cover.1747150490.git.asml.silence@gmail.com> (raw)
Random small improvements for provided buffers [un]registration,
with Patch 6 deduplicating and shrinking legacy pbuf buffer
management opcodes.
Pavel Begunkov (6):
io_uring/kbuf: account ring io_buffer_list memory
io_uring/kbuf: use mem_is_zero()
io_uring/kbuf: drop extra vars in io_register_pbuf_ring
io_uring/kbuf: don't compute size twice on prep
io_uring/kbuf: refactor __io_remove_buffers
io_uring/kbuf: unify legacy buf provision and removal
io_uring/kbuf.c | 131 +++++++++++++++++------------------------------
io_uring/kbuf.h | 4 +-
io_uring/opdef.c | 4 +-
3 files changed, 50 insertions(+), 89 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-13 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 17:26 Pavel Begunkov [this message]
2025-05-13 17:26 ` [PATCH 1/6] io_uring/kbuf: account ring io_buffer_list memory Pavel Begunkov
2025-05-13 20:47 ` Jens Axboe
2025-05-13 17:26 ` [PATCH 2/6] io_uring/kbuf: use mem_is_zero() Pavel Begunkov
2025-05-13 17:26 ` [PATCH 3/6] io_uring/kbuf: drop extra vars in io_register_pbuf_ring Pavel Begunkov
2025-05-13 17:26 ` [PATCH 4/6] io_uring/kbuf: don't compute size twice on prep Pavel Begunkov
2025-05-13 17:26 ` [PATCH 5/6] io_uring/kbuf: refactor __io_remove_buffers Pavel Begunkov
2025-05-13 17:26 ` [PATCH 6/6] io_uring/kbuf: unify legacy buf provision and removal Pavel Begunkov
2025-05-13 20:47 ` [PATCH 0/6] provided buffer cleanups 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.1747150490.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.