From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
"'LKML'" <linux-kernel@vger.kernel.org>,
"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
"'Christian Loehle'" <christian.loehle@arm.com>,
"'Artem Bityutskiy'" <artem.bityutskiy@linux.intel.com>,
"'Aboorva Devarajan'" <aboorvad@linux.ibm.com>,
"'Linux PM'" <linux-pm@vger.kernel.org>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: [RFT][PATCH v1] cpuidle: teo: Avoid selecting deepest idle state over-eagerly
Date: Mon, 10 Feb 2025 07:17:21 -0800 [thread overview]
Message-ID: <000e01db7bce$e1d3b8b0$a57b2a10$@telus.net> (raw)
In-Reply-To: <CAJZ5v0jELEw3yAoRFLPgEcfBRoUyd6tKSNHO2Q1O6_CoeR1Bng@mail.gmail.com>
On 2025.02.08 03:25 Rafael J. Wysocki wrote:
>On Sat, Feb 8, 2025 at 12:40 AM Doug Smythies <dsmythies@telus.net> wrote:
>> On 2025.02.04 12:58 Rafael J. Wysocki wrote:
>>>
>>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
... snip ...
>>
>> Test durations were >= 45 minutes each.
>>
>> Kernel 6.14-rc1: Includes cpuidle: teo: Cleanups and very frequent wakeups handling update
>> Average Idle Power: teo governor: 2.199 watts (+25.51%)
>> Average Idle power: menu governor: 1.873 watts (+6.91%)
>
> menu hasn't changed in 6.14-rc1, so this would be variation between
>runs I suppose.
Perhaps the way I presented my data wasn't the best method.
All the % were relative to kernel 6.13 and the teo idle governor.
Relative to kernel 6.13 menu governor that would be: -1.9%,
certainly within the noise floor.
>> Kernel 6.14-rc1-p: Added this patch for teo and "cpuidle: menu: Avoid discarding useful information when processing recent idle intervals" for menu
>> Average Idle Power: teo governor: 9.401 watts (+436.6%)
>> Only 69.61% idle is in the deepest idle state. More typically it would be 98% to 99%.
>
> Ah, not good.
>
> OK, this clearly doesn't go in the right direction.
>
>> 28.6531% idle time is in state 1. More typically it would be 0.03%
>> Average Idle Power: menu governor: 1.820 watts (+3.9%)
>>
>> Kernel 6.13: before "cpuidle: teo: Cleanups and very frequent wakeups handling update"
>> Average Idle Power: teo governor: 1.752 watts (reference: 0.0%)
>> Average Idle power: menu governor: 1.909 watts (+9.0%)
>
> Thanks, I'm just going to drop this patch then.
>
> If you don't mind, I'll have a couple more teo updates for testing.
O.K. I'll watch for the patches.
Plenty to do in the meantime, acquiring baseline data and continuing with the:
"cpuidle: menu: Avoid discarding useful information when processing recent idle intervals"
patch set portion of kernel 6.14-rc1-p
next prev parent reply other threads:[~2025-02-10 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 20:58 [RFT][PATCH v1] cpuidle: teo: Avoid selecting deepest idle state over-eagerly Rafael J. Wysocki
2025-02-06 14:37 ` Rafael J. Wysocki
2025-02-07 23:40 ` Doug Smythies
2025-02-08 11:24 ` Rafael J. Wysocki
2025-02-10 15:17 ` Doug Smythies [this message]
2025-02-09 9:24 ` Artem Bityutskiy
2025-02-10 15:17 ` Doug Smythies
2025-02-13 14:07 ` Christian Loehle
2025-02-14 4:23 ` Doug Smythies
2025-02-14 21:34 ` Rafael J. Wysocki
2025-02-18 11:28 ` Christian Loehle
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='000e01db7bce$e1d3b8b0$a57b2a10$@telus.net' \
--to=dsmythies@telus.net \
--cc=aboorvad@linux.ibm.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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