From: Lukasz Luba <lukasz.luba@arm.com>
To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
rafael@kernel.org
Cc: lukasz.luba@arm.com, viresh.kumar@linaro.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: [PATCH v3 0/1] cpufreq: schedutil: Optimize operations in hot path frequency switch
Date: Thu, 8 Dec 2022 16:02:55 +0000 [thread overview]
Message-ID: <20221208160256.859-1-lukasz.luba@arm.com> (raw)
Hi all,
This v3 is an attempt to optimize some of not needed operations in the frequency
change code path for the shared freq. domain. There was different approach
which was too aggressive and failed due to working on a stale CPU capacity
information.
changes:
v3:
- follow Vincent recommendation to drop the sg_policy::max, I have instead
tried to reduce the lookup and cache pressure, but use local var passing
to functions when needed
- unfortunately I couldn't use Viresh's ACKs for the v2 patches, since the code
has changed heavily
- updated the patch header with description of the code flow and the issue, since I
thought this optimization reason should be better explained, so people can refer
to it, since the former approach was reverted
v2:
- split the patch into two (Viresh)
v1:
- simple approach which fetches CPU capacity every time it's needed,
not relaying on the setup value, which was causing issues.
Regards,
Lukasz
Lukasz Luba (1):
cpufreq: schedutil: Optimize operations with single CPU capacity
lookup
kernel/sched/cpufreq_schedutil.c | 43 +++++++++++++++++---------------
1 file changed, 23 insertions(+), 20 deletions(-)
--
2.17.1
next reply other threads:[~2022-12-08 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 16:02 Lukasz Luba [this message]
2022-12-08 16:02 ` [PATCH v3 1/1] cpufreq: schedutil: Optimize operations with single CPU capacity lookup Lukasz Luba
2022-12-08 23:38 ` Viresh Kumar
2022-12-09 8:39 ` Lukasz Luba
2023-01-07 10:53 ` [tip: sched/core] cpufreq, sched/util: " tip-bot2 for Lukasz Luba
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=20221208160256.859-1-lukasz.luba@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®