Linux io-uring development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH 4/4] io_uring: add IORING_REGISTER_COPY_BUFFERS method
Date: Fri, 20 Sep 2024 00:16:22 -0600	[thread overview]
Message-ID: <1c02959b-030c-4993-b566-8b72b682a8e0@kernel.dk> (raw)
In-Reply-To: <87jzfagrle.fsf@mailhost.krisman.be>

On 9/17/24 10:41 AM, Gabriel Krisman Bertazi wrote:
> Jens Axboe <axboe@kernel.dk> writes:
> 
>> Buffers can get registered with io_uring, which allows to skip the
>> repeated pin_pages, unpin/unref pages for each O_DIRECT operation. This
>> reduces the overhead of O_DIRECT IO.
>>
>> However, registrering buffers can take some time. Normally this isn't an
>> issue as it's done at initialization time (and hence less critical), but
>> for cases where rings can be created and destroyed as part of an IO
>> thread pool, registering the same buffers for multiple rings become a
>> more time sensitive proposition. As an example, let's say an application
>> has an IO memory pool of 500G. Initial registration takes:
>>
>> Got 500 huge pages (each 1024MB)
>> Registered 500 pages in 409 msec
>>
>> or about 0.4 seconds. If we go higher to 900 1GB huge pages being
>> registered:
>>
>> Registered 900 pages in 738 msec
>>
>> which is, as expected, a fully linear scaling.
>>
>> Rather than have each ring pin/map/register the same buffer pool,
>> provide an io_uring_register(2) opcode to simply duplicate the buffers
>> that are registered with another ring. Adding the same 900GB of
>> registered buffers to the target ring can then be accomplished in:
>>
>> Copied 900 pages in 17 usec
>>
>> While timing differs a bit, this provides around a 25,000-40,000x
>> speedup for this use case.
> 
> Looks good, but I couldn't get it to apply on top of your branches.  I
> have only one comment, if you are doing a v4:
>>
>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>> ---
>>  include/uapi/linux/io_uring.h | 13 +++++
>>  io_uring/register.c           |  6 +++
>>  io_uring/rsrc.c               | 91 +++++++++++++++++++++++++++++++++++
>>  io_uring/rsrc.h               |  1 +
>>  4 files changed, 111 insertions(+)
>>
>> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h
> 
>> --- a/io_uring/rsrc.c
>> +++ b/io_uring/rsrc.c
>> @@ -17,6 +17,7 @@
>>  #include "openclose.h"
>>  #include "rsrc.h"
>>  #include "memmap.h"
>> +#include "register.h"
>>  
>>  struct io_rsrc_update {
>>  	struct file			*file;
>> @@ -1137,3 +1138,93 @@ int io_import_fixed(int ddir, struct iov_iter *iter,
>>  
>>  	return 0;
>>  }
>> +
>> +static int io_copy_buffers(struct io_ring_ctx *ctx, struct io_ring_ctx *src_ctx)
> 
> 
> The error handling code in this function is a bit hairy, IMO.  I think
> if you check nbufs unlocked and validate it later, it could be much
> simpler:

Sorry missed this due to travel - this is upstream in this merge window.
If you want to send a cleanup against for-6.12/io_uring, then please do!

-- 
Jens Axboe

      reply	other threads:[~2024-09-20  6:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 16:38 [PATCHSET v3 0/4] Provide more efficient buffer registration Jens Axboe
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 [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 \
    --in-reply-to=1c02959b-030c-4993-b566-8b72b682a8e0@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=krisman@suse.de \
    /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