From: Kajetan Puchalski <kajetan.puchalski@arm.com>
To: Doug Smythies <dsmythies@telus.net>
Cc: rafael@kernel.org, daniel.lezcano@linaro.org,
lukasz.luba@arm.com, Dietmar.Eggemann@arm.com,
yu.chen.surf@gmail.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/1] cpuidle: teo: Introduce optional util-awareness
Date: Mon, 10 Oct 2022 11:09:11 +0100 [thread overview]
Message-ID: <Y0PvRz83+lklWeyb@e126311.manchester.arm.com> (raw)
In-Reply-To: <CAAYoRsXgmwQXNzDPgVe=_cW=C8_7__GYHCyRKkfX=6dFY9dybw@mail.gmail.com>
On Thu, Oct 06, 2022 at 05:06:58PM -0700, Doug Smythies wrote:
>
> I would suggest a completely new governor for your
> only 2 idle states, and of similar power use, scenario.
> Incredibly simple:
>
> If CPU utilization >= threshold
> select idle state 0
> Else
> Select idle state 1
> Endif
That would be easy to implement at least but sadly just doesn't really
work at all. It would just result in huge amounts of too deep C1 sleeps
which are the main problem for us at the moment. For all intents and
purposes, only ever selecting C0 gives better results than this approach
on our hardware.
> As previously mentioned, you are overriding
> everything that teo does anyhow.
To an extent yes, this just came from observations of how cpuidle
behaves on arm. We tried an approach with only ever using C0 and it was
all right on power usage, the device would just heat up too much and
lose performance. That's why this approach of using TEO when the core is
completely idle and moving to the lower state when it's not achieves the
best of both worlds.
> Note to other readers: I also sent Kajetan an off-list email with more
> tests descriptions and web links to results graphs and such.
Looks like the email got lost in my inbox, could be some email filtering
or something like that.. Could you possibly resend and cc my private
email (kajetan.puchalski@tuta.io)?
So far I've not directly received any of your emails, they show up on
the mailing list archive but not in my inbox. Could be an IT issue on my
end but might be worth checking your email setup regardless.
> ... Doug
Thanks,
Kajetan
next prev parent reply other threads:[~2022-10-10 10:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 14:49 [RFC PATCH v2 0/1] cpuidle: teo: Introduce optional util-awareness Kajetan Puchalski
2022-10-03 14:49 ` [RFC PATCH v2 1/1] " Kajetan Puchalski
2022-10-07 0:06 ` [RFC PATCH v2 0/1] " Doug Smythies
2022-10-10 10:09 ` Kajetan Puchalski [this message]
2022-10-11 8:21 ` Lukasz Luba
2022-10-12 18:50 ` Rafael J. Wysocki
2022-10-13 11:12 ` Kajetan Puchalski
2022-10-13 22:12 ` Doug Smythies
2022-10-27 19:56 ` Lukasz Luba
2022-10-28 13:29 ` Rafael J. Wysocki
2022-10-27 20:04 ` Lukasz Luba
2022-10-28 13:37 ` Rafael J. Wysocki
2022-10-28 13:12 ` Rafael J. Wysocki
2022-10-28 15:00 ` Kajetan Puchalski
2022-10-28 15:04 ` Rafael J. Wysocki
2022-10-28 15:08 ` Rafael J. Wysocki
2022-10-20 16:20 ` Kajetan Puchalski
2022-10-20 19:52 ` Daniel Lezcano
2022-10-28 7:08 ` Lukasz Luba
2022-10-28 7:11 ` Daniel Lezcano
2022-10-28 7:23 ` Lukasz Luba
2022-10-28 13:25 ` Rafael J. Wysocki
2022-10-28 13:22 ` Rafael J. Wysocki
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=Y0PvRz83+lklWeyb@e126311.manchester.arm.com \
--to=kajetan.puchalski@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dsmythies@telus.net \
--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