From: "Doug Smythies" <dsmythies@telus.net>
To: "'Artem Bityutskiy'" <artem.bityutskiy@linux.intel.com>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
"'Christian Loehle'" <christian.loehle@arm.com>,
"'Aboorva Devarajan'" <aboorvad@linux.ibm.com>,
"'Linux PM'" <linux-pm@vger.kernel.org>,
"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
"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:20 -0800 [thread overview]
Message-ID: <000d01db7bce$e145f7a0$a3d1e6e0$@telus.net> (raw)
In-Reply-To: <38fadf14318be8f3c622719cc526f7586657e0e2.camel@linux.intel.com>
Hi Artem,
On 2025.02.09 01:15 : Artem Bityutskiy wrote:
> On Fri, 2025-02-07 at 15:40 -0800, Doug Smythies wrote:
>> I have only just started testing the recent idle governor changes,
>> and have not gotten very far yet.
>
> Hi Dough,
>
> there is the menu governor patch too. While it helps the server, I did not test
> it on a client system. May be you would to check it too? Subject is:
>
> [RFT][PATCH v1 0/5] cpuidle: menu: Avoid discarding useful information when processing recent idle intervals
Yes, I have included that patch set in my kernel 6.14-rc1 plus patches under test.
Other than the idle data, I don't have any other data to present yet as I have been
acquiring baseline data.
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
2025-02-09 9:24 ` Artem Bityutskiy
2025-02-10 15:17 ` Doug Smythies [this message]
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='000d01db7bce$e145f7a0$a3d1e6e0$@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