From: Hao Jia <jiahao.kernel@gmail.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>,
mingo@redhat.com, peterz@infradead.org, mingo@kernel.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com
Cc: linux-kernel@vger.kernel.org, Hao Jia <jiahao1@lixiang.com>,
Aaron Lu <ziqianlu@bytedance.com>
Subject: Re: [PATCH] sched/fair: Fix non-empty throttled_limbo_list warning in tg_throttle_down()
Date: Fri, 24 Oct 2025 14:58:41 +0800 [thread overview]
Message-ID: <561a15f5-3391-2796-6454-b980e0a228bd@gmail.com> (raw)
In-Reply-To: <98c1968e-8629-43d1-a4b8-600d263bd5a1@amd.com>
Hi Prateek,
On 2025/10/24 12:36, K Prateek Nayak wrote:
> Hello Hao,
>
> On 10/23/2025 5:42 PM, Hao Jia wrote:
>> @@ -5287,7 +5287,9 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
>> se->on_rq = 1;
>>
>> if (cfs_rq->nr_queued == 1) {
>> - check_enqueue_throttle(cfs_rq);
>> + if (!(flags & ENQUEUE_THROTTLE))
>> + check_enqueue_throttle(cfs_rq);
>> +
>
> So my only concern here is:
>
> check_enqueue_throttle()
> account_cfs_rq_runtime()
> __account_cfs_rq_runtime()
> assign_cfs_rq_runtime()
> __assign_cfs_rq_runtime()
> start_cfs_bandwidth() /* Starts the BW timer. */
>
> If we skip it, we wouldn't know we've run out of bandwidth until the
> hierarchy is picked which would cause additional delay until the
> bandwidth is replenished.
>
> At the very least, we should pass the enqueue flags to
> check_enqueue_throttle() and only skip the throttle_cfs_rq() part if
> we spot ENQUEUE_THROTTLE.
>
> Thoughts?
>
Thanks for your suggestion. This is indeed a potential risk, and it will
do it in the next version.
Thanks,
Hao
prev parent reply other threads:[~2025-10-24 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 12:12 Hao Jia
2025-10-24 3:39 ` Aaron Lu
2025-10-24 6:51 ` Hao Jia
2025-10-24 4:36 ` K Prateek Nayak
2025-10-24 6:58 ` Hao Jia [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 \
--in-reply-to=561a15f5-3391-2796-6454-b980e0a228bd@gmail.com \
--to=jiahao.kernel@gmail.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jiahao1@lixiang.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=ziqianlu@bytedance.com \
/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
all inboxes | Powered by JetHome®