From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Qais Yousef <qyousef@layalina.io>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Lukasz Luba <lukasz.luba@arm.com>, Wei Wang <wvw@google.com>,
Rick Yiu <rickyiu@google.com>,
Chung-Kai Mei <chungkai@google.com>,
Hongyan Xia <hongyan.xia2@arm.com>
Subject: Re: [PATCH 1/4] sched/fair: Be less aggressive in calling cpufreq_update_util()
Date: Tue, 12 Dec 2023 11:46:35 +0100 [thread overview]
Message-ID: <47ef274b-d9cc-4f4f-8134-2dced46005fa@arm.com> (raw)
In-Reply-To: <20231208015242.385103-2-qyousef@layalina.io>
On 08/12/2023 02:52, Qais Yousef wrote:
> Due to the way code is structured, it makes a lot of sense to trigger
> cpufreq_update_util() from update_load_avg(). But this is too aggressive
> as in most cases we are iterating through entities in a loop to
> update_load_avg() in the hierarchy. So we end up sending too many
> request in an loop as we're updating the hierarchy.
But update_load_avg() calls cfs_rq_util_change() which only issues a
cpufreq_update_util() call for the root cfs_rq?
So the 'iterating through entities' should be for a task in a non-root
taskgroup which the condition (1) takes care of.
cfs_rq_util_change()
...
if (&rq->cfs == cfs_rq) (1)
cpufreq_update_util()
[...]
next prev parent reply other threads:[~2023-12-12 10:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 1:52 [PATCH 0/4] sched: cpufreq: Remove uclamp max-aggregation Qais Yousef
2023-12-08 1:52 ` [PATCH 1/4] sched/fair: Be less aggressive in calling cpufreq_update_util() Qais Yousef
2023-12-08 10:05 ` Lukasz Luba
2023-12-10 20:51 ` Qais Yousef
2023-12-11 7:56 ` Lukasz Luba
2023-12-12 12:10 ` Qais Yousef
2023-12-14 8:19 ` Lukasz Luba
2023-12-11 18:47 ` Christian Loehle
2023-12-12 12:34 ` Qais Yousef
2023-12-12 13:09 ` Christian Loehle
2023-12-12 13:29 ` Qais Yousef
2023-12-12 10:46 ` Dietmar Eggemann [this message]
2023-12-12 12:35 ` Qais Yousef
2023-12-12 18:22 ` Hongyan Xia
2023-12-12 10:47 ` Hongyan Xia
2023-12-12 11:06 ` Vincent Guittot
2023-12-12 12:40 ` Qais Yousef
2023-12-29 0:25 ` Qais Yousef
2024-01-03 13:41 ` Vincent Guittot
2024-01-04 19:40 ` Qais Yousef
2023-12-18 8:51 ` Dietmar Eggemann
2023-12-17 21:44 ` Qais Yousef
2023-12-08 1:52 ` [PATCH 2/4] sched/uclamp: Remove rq max aggregation Qais Yousef
2023-12-11 0:08 ` Qais Yousef
2023-12-08 1:52 ` [PATCH 3/4] sched/schedutil: Ignore update requests for short running tasks Qais Yousef
2023-12-08 10:42 ` Hongyan Xia
2023-12-10 22:22 ` Qais Yousef
2023-12-11 11:15 ` Hongyan Xia
2023-12-12 12:23 ` Qais Yousef
2023-12-08 1:52 ` [PATCH 4/4] sched/documentation: Remove reference to max aggregation Qais Yousef
2023-12-18 8:19 ` [PATCH 0/4] sched: cpufreq: Remove uclamp max-aggregation Dietmar Eggemann
2023-12-17 21:23 ` Qais Yousef
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=47ef274b-d9cc-4f4f-8134-2dced46005fa@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=chungkai@google.com \
--cc=hongyan.xia2@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=rickyiu@google.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=wvw@google.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;
as well as URLs for NNTP newsgroup(s).