From: Lukasz Luba <lukasz.luba@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
rafael@kernel.org, dietmar.eggemann@arm.com,
vincent.guittot@linaro.org, saravanak@google.com,
wusamuel@google.com, isaacmanjarres@google.com,
kernel-team@android.com, juri.lelli@redhat.com,
peterz@infradead.org, mingo@redhat.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de
Subject: Re: [PATCH v2 2/2] cpufreq: schedutil: Optimize operations with single max CPU capacity
Date: Thu, 8 Dec 2022 08:43:16 +0000 [thread overview]
Message-ID: <a6b22f53-da3a-559b-9244-425ba0d7f9c3@arm.com> (raw)
In-Reply-To: <20221208040921.tgwegk7fvdm4nkiu@vireshk-i7>
On 12/8/22 04:09, Viresh Kumar wrote:
> On 07-12-22, 10:17, Lukasz Luba wrote:
>> The max CPU capacity is the same for all CPUs sharing frequency domain
>> and thus 'policy' object. There is a way to avoid heavy operations
>> in a loop for each CPU by leveraging this knowledge. Thus, simplify
>> the looping code in the sugov_next_freq_shared() and drop heavy
>> multiplications. Instead, use simple max() to get the highest utilization
>> from these CPUs. This is useful for platforms with many (4 or 6) little
>> CPUs.
>>
>> The max CPU capacity must be fetched every time we are called, due to
>> difficulties during the policy setup, where we are not able to get the
>> normalized CPU capacity at the right time.
>>
>> The stored value in sugov_policy::max is also than used in
>> sugov_iowait_apply() to calculate the right boost. Thus, that field is
>> useful to have in that sugov_policy struct.
>>
>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>> kernel/sched/cpufreq_schedutil.c | 22 +++++++++++-----------
>> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> Looks okay to me.
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
Thank you Viresh!
As Rafael said, it will wait after 6.2-rc1 is out.
Regards,
Lukasz
next prev parent reply other threads:[~2022-12-08 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 10:17 [PATCH v2 0/2] cpufreq: schedutil: Optimize operations in hot path frequency switch Lukasz Luba
2022-12-07 10:17 ` [PATCH v2 1/2] cpufreq: schedutil: Introduce single max CPU capacity for freqency domain Lukasz Luba
2022-12-08 3:57 ` Viresh Kumar
2022-12-07 10:17 ` [PATCH v2 2/2] cpufreq: schedutil: Optimize operations with single max CPU capacity Lukasz Luba
2022-12-08 4:09 ` Viresh Kumar
2022-12-08 8:43 ` Lukasz Luba [this message]
2022-12-08 8:37 ` Vincent Guittot
2022-12-08 10:06 ` Lukasz Luba
2022-12-08 10:31 ` Vincent Guittot
2022-12-08 10:56 ` Lukasz Luba
2022-12-08 13:20 ` Vincent Guittot
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=a6b22f53-da3a-559b-9244-425ba0d7f9c3@arm.com \
--to=lukasz.luba@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=isaacmanjarres@google.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=saravanak@google.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=wusamuel@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
all inboxes | Powered by JetHome®