From: Qais Yousef <qyousef@layalina.io>
To: Kajetan Puchalski <kajetan.puchalski@arm.com>
Cc: rafael@kernel.org, daniel.lezcano@linaro.org,
lukasz.luba@arm.com, Dietmar.Eggemann@arm.com,
dsmythies@telus.net, yu.chen.surf@gmail.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] cpuidle: teo: Introduce util-awareness
Date: Tue, 11 Jul 2023 18:58:14 +0100 [thread overview]
Message-ID: <20230711175814.zfavcn7xn3ia5va4@airbuntu> (raw)
In-Reply-To: <20230105145159.1089531-3-kajetan.puchalski@arm.com>
Hi Kajetan
On 01/05/23 14:51, Kajetan Puchalski wrote:
[...]
> @@ -510,9 +598,11 @@ static int teo_enable_device(struct cpuidle_driver *drv,
> struct cpuidle_device *dev)
> {
> struct teo_cpu *cpu_data = per_cpu_ptr(&teo_cpus, dev->cpu);
> + unsigned long max_capacity = arch_scale_cpu_capacity(dev->cpu);
> int i;
>
> memset(cpu_data, 0, sizeof(*cpu_data));
> + cpu_data->util_threshold = max_capacity >> UTIL_THRESHOLD_SHIFT;
Given that utilization is invariant, why do we set the threshold based on
cpu capacity?
I'm not sure if this is a problem, but on little cores this threshold would be
too low. Given that util is invariant - I wondered if we need to have a single
threshold for all type of CPUs instead. Have you tried something like that
while developing the patch?
Thanks
--
Qais Yousef
next prev parent reply other threads:[~2023-07-11 17:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 14:51 [PATCH v6 0/2] cpuidle: teo: Introduce util-awareness Kajetan Puchalski
2023-01-05 14:51 ` [PATCH v6 1/2] cpuidle: teo: Optionally skip polling states in teo_find_shallower_state() Kajetan Puchalski
2023-01-05 14:51 ` [PATCH v6 2/2] cpuidle: teo: Introduce util-awareness Kajetan Puchalski
2023-01-05 15:07 ` Rafael J. Wysocki
2023-01-05 15:20 ` Lukasz Luba
2023-01-05 15:34 ` Vincent Guittot
2023-01-05 17:11 ` Rafael J. Wysocki
2023-07-11 17:58 ` Qais Yousef [this message]
2023-07-17 13:47 ` Lukasz Luba
2023-07-17 18:21 ` Qais Yousef
2023-07-18 10:23 ` Lukasz Luba
2023-07-18 12:45 ` Qais Yousef
2023-07-18 12:02 ` Kajetan Puchalski
2023-07-18 13:24 ` Qais Yousef
2023-07-19 15:07 ` Kajetan Puchalski
2023-09-17 1:05 ` Qais Yousef
2023-09-18 11:41 ` Kajetan Puchalski
2023-09-19 0:04 ` Qais Yousef
2024-05-28 9:29 ` Vincent Guittot
2024-05-28 9:59 ` Lukasz Luba
2024-05-28 14:07 ` Vincent Guittot
2024-05-29 13:09 ` Christian Loehle
2024-05-31 8:57 ` Vincent Guittot
2024-06-12 7:25 ` Lukasz Luba
2024-06-12 9:04 ` Vincent Guittot
2024-06-12 9:17 ` Lukasz Luba
2024-06-17 8:52 ` Vincent Guittot
2024-06-19 12:20 ` Lukasz Luba
2024-05-28 10:35 ` Christian Loehle
2024-05-28 12:12 ` Kajetan Puchalski
2024-05-29 10:23 ` Qais Yousef
2024-05-29 10:19 ` Qais Yousef
2024-06-12 7:53 ` Lukasz Luba
2024-06-16 21:48 ` Qais Yousef
2024-06-17 8:13 ` Lukasz Luba
2023-01-12 19:22 ` [PATCH v6 0/2] " Rafael J. Wysocki
2023-01-13 15:21 ` Kajetan Puchalski
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=20230711175814.zfavcn7xn3ia5va4@airbuntu \
--to=qyousef@layalina.io \
--cc=Dietmar.Eggemann@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dsmythies@telus.net \
--cc=kajetan.puchalski@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=yu.chen.surf@gmail.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