From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linexp.org>
Cc: Dietmar.Eggemann@arm.com, dsmythies@telus.net,
Kajetan Puchalski <kajetan.puchalski@arm.com>,
yu.chen.surf@gmail.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [RFC PATCH v2 0/1] cpuidle: teo: Introduce optional util-awareness
Date: Fri, 28 Oct 2022 08:23:33 +0100 [thread overview]
Message-ID: <63a63f5e-846a-3235-56f9-3cc9b5c2dd4d@arm.com> (raw)
In-Reply-To: <ac249d3c-6907-daf5-1047-0b3823eef1aa@linexp.org>
On 10/28/22 08:11, Daniel Lezcano wrote:
> On 28/10/2022 09:08, Lukasz Luba wrote:
>
> [ ... ]
>
>>> [1] Dynamic workload characterization for power efficient scheduling
>>> on CMP systems : https://cseweb.ucsd.edu//~tullsen/islped10.pdf
>>>
>>> [2]
>>> https://git.linaro.org/people/daniel.lezcano/linux.git/commit/?h=cpuidle/mobile-governor-v5.1&id=de1edb05e3c342f0738b414aa84263d6555b7462
>>>
>>>
>>>
>>
>> Thanks Daniel! I forgot about your work in this area. As I have
>> responded in some other email in this thread, we might start
>> from a new small governor and than others can contribute.
>>
>> Even this small governor that Kajetan showed me performs really
>> good on pixel6.
>
> Do you have others ARM64 platforms to compare with ?
>
Yes we have, also some older platforms (~10years now, which
would be nice to check how they would perform).
We also have a big arm64 server to give it a try there. So those results
will be available with the new patch when we decide to go the new
governor.
next prev parent reply other threads:[~2022-10-28 7:23 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
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 [this message]
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=63a63f5e-846a-3235-56f9-3cc9b5c2dd4d@arm.com \
--to=lukasz.luba@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=daniel.lezcano@linexp.org \
--cc=dsmythies@telus.net \
--cc=kajetan.puchalski@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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