From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH for-next 0/6] cleanup task/files cancel
Date: Mon, 9 Nov 2020 07:43:04 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/6/20 6:00 AM, Pavel Begunkov wrote:
> That unifies cancellation/matching/etc., so we can kill all that going
> out of hand zoo of functions.
>
> Jens, [3/6] changes the behaviour, but as last time it's less
> restrictive and doesn't kill what we don't need to kill. Though, it'd
> prefer you to check the assumption in light of the cancel changes you've
> done.
>
> Based on for-5.11/io_uring + "io_uring: fix link lookup racing with link
> timeout", should apply ok after you merge everything.
>
> Pavel Begunkov (6):
> io_uring: simplify io_task_match()
> io_uring: add a {task,files} pair matching helper
> io_uring: cancel only requests of current task
> io_uring: don't iterate io_uring_cancel_files()
> io_uring: pass files into kill timeouts/poll
> io_uring: always batch cancel in *cancel_files()
>
> fs/io-wq.c | 10 --
> fs/io-wq.h | 1 -
> fs/io_uring.c | 260 ++++++++++++++------------------------------------
> 3 files changed, 69 insertions(+), 202 deletions(-)
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-11-09 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 13:00 [PATCH for-next 0/6] cleanup task/files cancel Pavel Begunkov
2020-11-06 13:00 ` [PATCH 1/6] io_uring: simplify io_task_match() Pavel Begunkov
2020-11-06 13:00 ` [PATCH 2/6] io_uring: add a {task,files} pair matching helper Pavel Begunkov
2020-11-06 13:00 ` [PATCH 3/6] io_uring: cancel only requests of current task Pavel Begunkov
2020-11-06 13:00 ` [PATCH 4/6] io_uring: don't iterate io_uring_cancel_files() Pavel Begunkov
2020-11-06 13:00 ` [PATCH 5/6] io_uring: pass files into kill timeouts/poll Pavel Begunkov
2020-11-06 13:00 ` [PATCH 6/6] io_uring: always batch cancel in *cancel_files() Pavel Begunkov
2020-11-09 14:43 ` 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