From: Bijan Mottahedeh <[email protected]>
To: Jens Axboe <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH v4 00/13] io_uring: buffer registration enhancements
Date: Thu, 7 Jan 2021 09:03:23 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/7/2021 7:53 AM, Jens Axboe wrote:
> On 1/6/21 1:39 PM, Bijan Mottahedeh wrote:
>> v4:
>>
>> - address v3 comments (TBD REGISTER_BUFFERS)
>> - rebase
>>
>> v3:
>>
>> - batch file->rsrc renames into a signle patch when possible
>> - fix other review changes from v2
>> - fix checkpatch warnings
>>
>> v2:
>>
>> - drop readv/writev with fixed buffers patch
>> - handle ref_nodes both both files/buffers with a single ref_list
>> - make file/buffer handling more unified
>>
>> This patchset implements a set of enhancements to buffer registration
>> consistent with existing file registration functionality:
>>
>> - buffer registration updates IORING_REGISTER_BUFFERS_UPDATE
>> IORING_OP_BUFFERS_UPDATE
>>
>> - buffer registration sharing IORING_SETUP_SHARE_BUF
>> IORING_SETUP_ATTACH_BUF
>>
>> I have kept the original patchset unchanged for the most part to
>> facilitate reviewing and so this set adds a number of additional patches
>> mostly making file/buffer handling more unified.
>>
>> Patch 1-2 modularize existing buffer registration code.
>
> Applied 1-2 for now with Pavel's review, hopefully we can crank through
> the rest of the series and target 5.12.
>
Thanks. As for the other patches, #13 needs some attention based on
Pavel's observations regarding possible deadlocks. Can you have a look
at the discussion for that patch in the v2 series?
prev parent reply other threads:[~2021-01-07 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 20:39 [PATCH v4 00/13] io_uring: buffer registration enhancements Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 01/13] io_uring: modularize io_sqe_buffer_register Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 02/13] io_uring: modularize io_sqe_buffers_register Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 03/13] io_uring: rename file related variables to rsrc Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 04/13] io_uring: generalize io_queue_rsrc_removal Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 05/13] io_uring: separate ref_list from fixed_rsrc_data Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 06/13] io_uring: split alloc_fixed_file_ref_node Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 07/13] io_uring: add rsrc_ref locking routines Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 08/13] io_uring: implement fixed buffers registration similar to fixed files Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 09/13] io_uring: create common fixed_rsrc_ref_node handling routines Bijan Mottahedeh
2021-01-08 1:57 ` Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 10/13] io_uring: generalize files_update functionlity to rsrc_update Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 11/13] io_uring: support buffer registration updates Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 12/13] io_uring: create common fixed_rsrc_data allocation routines Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 13/13] io_uring: support buffer registration sharing Bijan Mottahedeh
2021-01-07 15:53 ` [PATCH v4 00/13] io_uring: buffer registration enhancements Jens Axboe
2021-01-07 17:03 ` Bijan Mottahedeh [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] \
[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