From: Shijie Huang <shijie@amperemail.onmicrosoft.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Huang Shijie <shijie@os.amperecomputing.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
patches@amperecomputing.com, cl@linux.com,
Shubhang@os.amperecomputing.com, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org, vschneid@redhat.com,
vineethr@linux.ibm.com, kprateek.nayak@amd.com
Subject: Re: [PATCH v6 2/2] sched: update the rq->avg_idle when a task is moved to an idle CPU
Date: Tue, 16 Dec 2025 15:38:55 +0800 [thread overview]
Message-ID: <c46d3964-9153-4656-8ff3-08bf9ae50702@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <CAKfTPtBn4YnqB0ySomYH6CVY99bz3wswaGuZQnPjsXE_T_A90g@mail.gmail.com>
On 16/12/2025 15:17, Vincent Guittot wrote:
> On Tue, 16 Dec 2025 at 07:22, Shijie Huang
> <shijie@amperemail.onmicrosoft.com> wrote:
>>
>> On 13/12/2025 09:36, Vincent Guittot wrote:
>>> put_prev_task_idle() would be a better place to call
>>> update_rq_avg_idle() because this is when we leave idle.
>> The update_rq_avg_idle() is not only called by current CPU, but also
>> called by
>>
>> other CPUs. For example, the try_to_wake_up(), update_rq_avg_idle() is
>> called by
>>
>> the other CPUs. So enqueue_task() is a good place.
> But put_prev_task_idle() is called by local CPU whenever it leaves
> idle so instead of trying to catch all places that could make the CPU
> leave idle it's better to use this single place.
> And as you mentioned, put_prev_task_idle is only called by local CPU
> whereas enqueue_task can be called by all CPUs creating useless
> pressure in the variable.
The rq->idle_stamp is set at sched_balance_newidle(). then we call
update_rq_avg_idle()
in put_prev_task_idle() right now. How can we update the rq->avg_idle?
Thanks
Huang Shijie
>>
next prev parent reply other threads:[~2025-12-16 7:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 9:45 [PATCH v6 0/2] " Huang Shijie
2025-12-09 9:45 ` [PATCH v6 1/2] sched/fair: set rq->idle_stamp at the end of the sched_balance_newidle Huang Shijie
2025-12-09 9:45 ` [PATCH v6 2/2] sched: update the rq->avg_idle when a task is moved to an idle CPU Huang Shijie
2025-12-11 16:15 ` Dietmar Eggemann
2025-12-12 3:16 ` Shijie Huang
2025-12-12 14:22 ` Dietmar Eggemann
2025-12-15 9:35 ` Shijie Huang
2025-12-17 16:15 ` Dietmar Eggemann
2026-01-07 15:48 ` Dietmar Eggemann
2026-01-09 13:33 ` Vincent Guittot
2025-12-13 1:36 ` Vincent Guittot
2025-12-16 6:22 ` Shijie Huang
2025-12-16 7:17 ` Vincent Guittot
2025-12-16 7:38 ` Shijie Huang [this message]
2025-12-16 8:47 ` Vincent Guittot
2025-12-16 9:49 ` Shijie Huang
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=c46d3964-9153-4656-8ff3-08bf9ae50702@amperemail.onmicrosoft.com \
--to=shijie@amperemail.onmicrosoft.com \
--cc=Shubhang@os.amperecomputing.com \
--cc=bsegall@google.com \
--cc=cl@linux.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=patches@amperecomputing.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shijie@os.amperecomputing.com \
--cc=vincent.guittot@linaro.org \
--cc=vineethr@linux.ibm.com \
--cc=vschneid@redhat.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®