From: Jens Axboe <[email protected]>
To: [email protected]
Subject: Re: [PATCHSET 0/3] Provide more efficient buffer registration
Date: Wed, 11 Sep 2024 14:13:10 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/11/24 2:03 PM, Jens Axboe wrote:
> 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, and patch 3 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.
Ignore this one, it was an old version... I'll send a v2 in a bit.
--
Jens Axboe
prev parent reply other threads:[~2024-09-11 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 20:03 [PATCHSET 0/3] Provide more efficient buffer registration Jens Axboe
2024-09-11 20:03 ` [PATCH 1/3] io_uring/rsrc: clear 'slot' entry upfront Jens Axboe
2024-09-11 20:03 ` [PATCH 2/3] io_uring/rsrc: add reference count to struct io_mapped_ubuf Jens Axboe
2024-09-11 20:03 ` [PATCH 3/3] io_uring: add IORING_REGISTER_COPY_BUFFERS method Jens Axboe
2024-09-11 20:13 ` Jens Axboe [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
/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