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 v2 0/2] cpufreq: schedutil: Optimize operations in hot path frequency switch
Date: Wed, 7 Dec 2022 10:17:03 +0000 [thread overview]
Message-ID: <20221207101705.9460-1-lukasz.luba@arm.com> (raw)
Hi all,
This v2 is an attempt to optimize some not needed operations in the frequency
change code path for the shared freq. domain. There was different approach
which was too aggressive and failed do to working on a state CPU capacity
information.
changes:
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 (2):
cpufreq: schedutil: Introduce single max CPU capacity for freqency
domain
cpufreq: schedutil: Optimize operations with single max CPU capacity
kernel/sched/cpufreq_schedutil.c | 35 +++++++++++++++++++-------------
1 file changed, 21 insertions(+), 14 deletions(-)
--
2.17.1
next reply other threads:[~2022-12-07 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 10:17 Lukasz Luba [this message]
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
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=20221207101705.9460-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®