From: Hao Xu <[email protected]>
To: Pavel Begunkov <[email protected]>, Jens Axboe <[email protected]>
Cc: [email protected], Joseph Qi <[email protected]>
Subject: Re: [PATCH] io_uring: update sq_thread_idle after ctx deleted
Date: Sun, 25 Apr 2021 17:52:17 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
在 2021/4/25 上午8:03, Pavel Begunkov 写道:
> On 4/24/21 10:26 AM, Hao Xu wrote:
>> we shall update sq_thread_idle anytime we do ctx deletion from ctx_list
>
> looks good, a nit below
>
>>
>> Fixes:734551df6f9b ("io_uring: fix shared sqpoll cancellation hangs")
>> Signed-off-by: Hao Xu <[email protected]>
>> ---
>> fs/io_uring.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/io_uring.c b/fs/io_uring.c
>> index 40f38256499c..15f204274761 100644
>> --- a/fs/io_uring.c
>> +++ b/fs/io_uring.c
>> @@ -8867,6 +8867,7 @@ static void io_sqpoll_cancel_cb(struct callback_head *cb)
>> if (sqd->thread)
>> io_uring_cancel_sqpoll(sqd);
>> list_del_init(&work->ctx->sqd_list);
>> + io_sqd_update_thread_idle(sqd);
>> complete(&work->completion);
>> }
>>
>> @@ -8877,7 +8878,6 @@ static void io_sqpoll_cancel_sync(struct io_ring_ctx *ctx)
>> struct task_struct *task;
>>
>> io_sq_thread_park(sqd);
>> - io_sqd_update_thread_idle(sqd);
>> task = sqd->thread;
>> if (task) {
>> init_completion(&work.completion);
>> @@ -8886,6 +8886,7 @@ static void io_sqpoll_cancel_sync(struct io_ring_ctx *ctx)
>> wake_up_process(task);
>> } else {
>> list_del_init(&ctx->sqd_list);
>> + io_sqd_update_thread_idle(sqd);
>
> Not actually needed, it's already dying.
>
Yep, we could keep it since it's not in hot path.
>> }
>> io_sq_thread_unpark(sqd);
>>
>>
>
next prev parent reply other threads:[~2021-04-25 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 9:26 [PATCH] io_uring: update sq_thread_idle after ctx deleted Hao Xu
2021-04-25 0:03 ` Pavel Begunkov
2021-04-25 9:52 ` Hao Xu [this message]
2021-04-25 16:15 ` 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 \
--in-reply-to=003de007-b289-96f8-ba0c-ff71e8c550a7@linux.alibaba.com \
[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