From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH v2 0/6] bunch of random fixes
Date: Mon, 4 Jan 2021 16:27:15 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 04/01/2021 01:59, Pavel Begunkov wrote:
> v2:
> - add 3/6 to trigger eventfd for iopoll
> - add 5/6, yet another iopoll sync fix
> - rework 6/6 (Jens)
I'll go with v3, probably splitting the series.
Apart from small changes I want to add, during long runs,
it kills tests with SIGINT, mainly 500f9fbadef8-test.
Any ideas what it can be?
>
> Pavel Begunkov (6):
> io_uring: drop file refs after task cancel
> io_uring: cancel more aggressively in exit_work
> io_uring: trigger eventfd for IOPOLL
> io_uring: dont kill fasync under completion_lock
> io_uring: synchronise IOPOLL on task_submit fail
> io_uring: patch up IOPOLL overflow_flush sync
>
> fs/io_uring.c | 146 ++++++++++++++++++++++++++++++--------------------
> 1 file changed, 87 insertions(+), 59 deletions(-)
>
--
Pavel Begunkov
prev parent reply other threads:[~2021-01-04 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 1:59 [PATCH v2 0/6] bunch of random fixes Pavel Begunkov
2021-01-04 1:59 ` [PATCH v2 1/6] io_uring: drop file refs after task cancel Pavel Begunkov
2021-01-04 1:59 ` [PATCH v2 2/6] io_uring: cancel more aggressively in exit_work Pavel Begunkov
2021-01-04 1:59 ` [PATCH v2 3/6] io_uring: trigger eventfd for IOPOLL Pavel Begunkov
2021-01-04 1:59 ` [PATCH v2 4/6] io_uring: dont kill fasync under completion_lock Pavel Begunkov
2021-01-04 1:59 ` [PATCH v2 5/6] io_uring: synchronise IOPOLL on task_submit fail Pavel Begunkov
2021-01-04 1:59 ` [PATCH v2 6/6] io_uring: patch up IOPOLL overflow_flush sync Pavel Begunkov
2021-01-04 16:27 ` Pavel Begunkov [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