From: Bijan Mottahedeh <[email protected]>
To: Pavel Begunkov <[email protected]>,
Jens Axboe <[email protected]>,
[email protected]
Subject: Re: [PATCH 0/9] Bijan's rsrc generalisation + prep parts
Date: Fri, 15 Jan 2021 10:24:11 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/15/2021 9:37 AM, Pavel Begunkov wrote:
> I guess we can agree that generic rsrc handling is a good thing to have,
> even if we have only files at the moment. This consists of related
> patches from the Bijan's longer series, doesn't include sharing and
> buffer bits. I suggest to merge it first. It's approx half of the all
> changes.
>
> Based on 5.12 with a few pathes from 5.11 cherry-pick to reduce merge
> conflicts, because of merging/etc. may wait for a week or so for the
> next rc before potentially being merged. This also addressed tricky
> merge conflicts where it was applying and compiling well but still
> buggy.
>
> Bijan, for the changed patches I also dropped your signed-off, so
> please reply if you're happy with the new versions so we can
> add it back. There are change logs (e.g. [did so]) in commit messages
> of those.
Looks good, thanks. I'll wait for your review of the buffer sharing
patch, and once this series is picked up, I'll resend the buffers
patches set.
>
> Mapping to the original v5 series:
> 1-5/9 (1-5/13 originally), mostly unchanged
> 6/9 -- my own prep
> 7/9 (7/13 originally), only file part
> 8/9 (10/13 originally), only file part
> 9/9 (11/13 before), unchanged
>
> Bijan Mottahedeh (8):
> io_uring: rename file related variables to rsrc
> io_uring: generalize io_queue_rsrc_removal
> io_uring: separate ref_list from fixed_rsrc_data
> io_uring: add rsrc_ref locking routines
> io_uring: split alloc_fixed_file_ref_node
> io_uring: create common fixed_rsrc_ref_node handling routines
> io_uring: create common fixed_rsrc_data allocation routines
> io_uring: make percpu_ref_release names consistent
>
> Pavel Begunkov (1):
> io_uring: split ref_node alloc and init
>
> fs/io_uring.c | 355 ++++++++++++++++++++--------------
> include/uapi/linux/io_uring.h | 7 +
> 2 files changed, 216 insertions(+), 146 deletions(-)
>
next prev parent reply other threads:[~2021-01-15 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 17:37 [PATCH 0/9] Bijan's rsrc generalisation + prep parts Pavel Begunkov
2021-01-15 17:37 ` [PATCH 1/9] io_uring: rename file related variables to rsrc Pavel Begunkov
2021-01-15 17:37 ` [PATCH 2/9] io_uring: generalize io_queue_rsrc_removal Pavel Begunkov
2021-01-15 17:37 ` [PATCH 3/9] io_uring: separate ref_list from fixed_rsrc_data Pavel Begunkov
2021-01-15 17:37 ` [PATCH 4/9] io_uring: add rsrc_ref locking routines Pavel Begunkov
2021-01-15 17:37 ` [PATCH 5/9] io_uring: split alloc_fixed_file_ref_node Pavel Begunkov
2021-01-15 17:37 ` [PATCH 6/9] io_uring: split ref_node alloc and init Pavel Begunkov
2021-01-15 17:37 ` [PATCH 7/9] io_uring: create common fixed_rsrc_ref_node handling routines Pavel Begunkov
2021-01-15 17:37 ` [PATCH 8/9] io_uring: create common fixed_rsrc_data allocation routines Pavel Begunkov
2021-01-15 17:37 ` [PATCH 9/9] io_uring: make percpu_ref_release names consistent Pavel Begunkov
2021-01-15 18:24 ` Bijan Mottahedeh [this message]
2021-01-15 19:08 ` [PATCH 0/9] Bijan's rsrc generalisation + prep parts 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 \
[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