From: "Doug Smythies" <dsmythies@telus.net>
To: "'Christian Loehle'" <christian.loehle@arm.com>,
"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
"'Linux PM'" <linux-pm@vger.kernel.org>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
"'Artem Bityutskiy'" <artem.bityutskiy@linux.intel.com>,
"'Aboorva Devarajan'" <aboorvad@linux.ibm.com>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: [RFT][PATCH v1] cpuidle: teo: Avoid selecting deepest idle state over-eagerly
Date: Thu, 13 Feb 2025 20:23:21 -0800 [thread overview]
Message-ID: <003a01db7e98$2e9ad770$8bd08650$@telus.net> (raw)
In-Reply-To: <8d147f4f-f511-4f44-b18e-2011b0fab17c@arm.com>
Hi Christian,
Thank you for trying to repeat my idle test results.
On 2025.02.13 06:07 Christian Loehle wrote:
> I'm curious, are Doug's numbers reproducible?
> Or could you share the idle state usage numbers? Is that explainable?
> Seems like a lot and it does worry me that I can't reproduce anything
> as drastic.
While I am having some severe repeatability issues with my testing,
not for this test.
Please recall my test conditions because the CPU frequency
scaling governor does matter. I was using "performance".
The power comes from the high amount of time in idle state 1.
I verified the idle state 1 power use by disabling all other idle states.
I also have HWP disabled, but do not know if it matters.
If I use the "powersave" governor (driver is intel_pstate, not
intel_cpufreq) then idle power is < 2 watts.
Anyway, my data:
http://smythies.com/~doug/linux/idle/teo-6.14/idle/perf/
> (Idle numbers aren't really reflective in energy used -> dominated by
> active power.)
Well, it depends on idle time verses active time on the computer.
I also measured the difference in the mains power at 20%, from
43.2 watts to 51.4 watts.
I am about to send a long email with all of my test results.
Since I can not seem to function without making graphs,
it has a lot of links to graphs.
next prev parent reply other threads:[~2025-02-14 4:23 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
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 [this message]
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='003a01db7e98$2e9ad770$8bd08650$@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=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