From: Xiaoguang Wang <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: [RFC PATCH] io_uring: don't submit sqes when ctx->refs is dying
Date: Wed, 13 May 2020 23:36:31 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
hi,
> On 5/13/20 6:37 AM, Xiaoguang Wang wrote:
>> When IORING_SETUP_SQPOLL is enabled, io_ring_ctx_wait_and_kill() will wait
>> for sq thread to idle by busy loop:
>> while (ctx->sqo_thread && !wq_has_sleeper(&ctx->sqo_wait))
>> cond_resched();
>> Above codes are not friendly, indeed I think this busy loop will introduce a
>> cpu burst in current cpu, though it maybe short.
>>
>> In this patch, if ctx->refs is dying, we forbids sq_thread from submitting
>> sqes anymore, just discard leftover sqes.
>
> I don't think this really changes anything. What happens if:
>
>> @@ -6051,7 +6053,8 @@ static int io_sq_thread(void *data)
>> }
>>
>> mutex_lock(&ctx->uring_lock);
>> - ret = io_submit_sqes(ctx, to_submit, NULL, -1, true);
>> + if (likely(!percpu_ref_is_dying(&ctx->refs)))
>> + ret = io_submit_sqes(ctx, to_submit, NULL, -1, true);
>> mutex_unlock(&ctx->uring_lock);
>> timeout = jiffies + ctx->sq_thread_idle;
>
> You check for dying here, but that could change basically while you're
> checking it. So you're still submitting sqes with a ref that's going
> away. You've only reduced the window, you haven't eliminated it.
Look at codes, we call percpu_ref_kill() under uring_lock, so isn't it safe
to check the refs' dying status? Thanks.
Regards,
Xiaouang Wang
>
next prev parent reply other threads:[~2020-05-13 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 12:37 [RFC PATCH] io_uring: don't submit sqes when ctx->refs is dying Xiaoguang Wang
2020-05-13 15:25 ` Jens Axboe
2020-05-13 15:36 ` Xiaoguang Wang [this message]
2020-05-16 9:23 ` Xiaoguang Wang
2020-05-19 15:45 ` Jens Axboe
2020-05-20 3:22 ` Xiaoguang Wang
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=1a5e92d0-02c7-44d9-07e5-50c0ca77b800@linux.alibaba.com \
[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