From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH RESEND for-next 00/12] 5.13 first batch
Date: Mon, 1 Mar 2021 16:53:49 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/28/21 3:35 PM, Pavel Begunkov wrote:
> 1-7 are just random stuff
> 8-12 are further cleanups for around prep_async
>
> based on io_uring-worker.v4, but should apply fine to for-next
>
> Pavel Begunkov (12):
> io_uring: avoid taking ctx refs for task-cancel
> io_uring: reuse io_req_task_queue_fail()
> io_uring: further deduplicate file slot selection
> io_uring: add a helper failing not issued requests
> io_uring: refactor provide/remove buffer locking
> io_uring: don't restirct issue_flags for io_openat
> io_uring: use better types for cflags
> io_uring: refactor out send/recv async setup
> io_uring: untie alloc_async_data and needs_async_data
> io_uring: rethink def->needs_async_data
> io_uring: merge defer_prep() and prep_async()
> io_uring: simplify io_resubmit_prep()
>
> fs/io_uring.c | 210 ++++++++++++++++----------------------------------
> 1 file changed, 68 insertions(+), 142 deletions(-)
>
Thanks, I've queued this up for 5.13 - I'll most likely rebase this
branch a few times going forward, until we have 5.12 fully settled.
--
Jens Axboe
prev parent reply other threads:[~2021-03-02 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 22:35 [PATCH RESEND for-next 00/12] 5.13 first batch Pavel Begunkov
2021-02-28 22:35 ` [PATCH 01/12] io_uring: avoid taking ctx refs for task-cancel Pavel Begunkov
2021-02-28 22:35 ` [PATCH 02/12] io_uring: reuse io_req_task_queue_fail() Pavel Begunkov
2021-02-28 22:35 ` [PATCH 03/12] io_uring: further deduplicate file slot selection Pavel Begunkov
2021-02-28 22:35 ` [PATCH 04/12] io_uring: add a helper failing not issued requests Pavel Begunkov
2021-02-28 22:35 ` [PATCH 05/12] io_uring: refactor provide/remove buffer locking Pavel Begunkov
2021-02-28 22:35 ` [PATCH 06/12] io_uring: don't restirct issue_flags for io_openat Pavel Begunkov
2021-02-28 22:35 ` [PATCH 07/12] io_uring: use better types for cflags Pavel Begunkov
2021-02-28 22:35 ` [PATCH 08/12] io_uring: refactor out send/recv async setup Pavel Begunkov
2021-02-28 22:35 ` [PATCH 09/12] io_uring: untie alloc_async_data and needs_async_data Pavel Begunkov
2021-02-28 22:35 ` [PATCH 10/12] io_uring: rethink def->needs_async_data Pavel Begunkov
2021-02-28 22:35 ` [PATCH 11/12] io_uring: merge defer_prep() and prep_async() Pavel Begunkov
2021-02-28 22:35 ` [PATCH 12/12] io_uring: simplify io_resubmit_prep() Pavel Begunkov
2021-03-01 23:53 ` 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] \
[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