From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET v3 0/4] Provide more efficient buffer registration
Date: Thu, 12 Sep 2024 10:38:19 -0600 [thread overview]
Message-ID: <20240912164019.634560-1-axboe@kernel.dk> (raw)
Hi,
Pretty much what the subject line says, it's about 25k to 40k times
faster to provide a way to duplicate an existing rings buffer
registration than it is manually map/pin/register the buffers again
with a new ring.
Patch 1 is just a prep patch, patch 2 adds refs to struct
io_mapped_ubuf, patch 3 abstracts out a helper, and patch 4 finally adds
the register opcode to allow a ring to duplicate the registered mappings
from one ring to another.
This came about from discussing overhead from the varnish cache
project for cases with more dynamic ring/thread creation.
Also see the buf-copy liburing branch for support and test code:
https://git.kernel.dk/cgit/liburing/log/?h=buf-copy
include/uapi/linux/io_uring.h | 13 +++++
io_uring/register.c | 60 ++++++++++++++--------
io_uring/register.h | 1 +
io_uring/rsrc.c | 96 ++++++++++++++++++++++++++++++++++-
io_uring/rsrc.h | 2 +
5 files changed, 150 insertions(+), 22 deletions(-)
Since v2:
- Ensure that it works for registered rings (both src/dst)
- Little cleanups
--
Jens Axboe
next reply other threads:[~2024-09-12 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 16:38 Jens Axboe [this message]
2024-09-12 16:38 ` [PATCH 1/4] io_uring/rsrc: clear 'slot' entry upfront Jens Axboe
2024-09-12 16:38 ` [PATCH 2/4] io_uring/rsrc: add reference count to struct io_mapped_ubuf Jens Axboe
2024-09-12 16:38 ` [PATCH 3/4] io_uring/register: provide helper to get io_ring_ctx from 'fd' Jens Axboe
2024-09-12 16:38 ` [PATCH 4/4] io_uring: add IORING_REGISTER_COPY_BUFFERS method Jens Axboe
2024-09-17 16:41 ` Gabriel Krisman Bertazi
2024-09-20 6:16 ` 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=20240912164019.634560-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--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.