From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, [email protected]
Cc: Jens Axboe <[email protected]>, Joseph Qi <[email protected]>
Subject: Re: [PATCH 5.15] io_uring: apply max_workers limit to all future users
Date: Wed, 20 Oct 2021 11:48:34 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 10/20/21 09:52, Hao Xu wrote:
> 在 2021/10/20 上午6:43, Pavel Begunkov 写道:
> Hi Pavel,
> The ctx->iowq_limits_set limits the future ctx users, but not the past
> ones, how about update the numbers for all the current ctx users here?
> I know the number of workers that a current user uses may already
> exceeds the newest limitation, but at least this will make it not to
> grow any more, and may decrement it to the limitation some time later.
Indeed, that was the idea! Though it's a bit trickier, would need
ctx->tctx_list traversal, and before putting it in I wanted to take
a look at another problem related to ->tctx_list. I hope to get that
done asap for 5.15.
--
Pavel Begunkov
prev parent reply other threads:[~2021-10-20 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 22:43 [PATCH 5.15] io_uring: apply max_workers limit to all future users Pavel Begunkov
2021-10-19 23:14 ` Jens Axboe
2021-10-20 0:23 ` Jens Axboe
2021-10-20 8:52 ` Hao Xu
2021-10-20 10:48 ` 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] \
[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