[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000d01db7bce$e145f7a0$a3d1e6e0$@telus.net>
Date: Mon, 10 Feb 2025 07:17:20 -0800
From: "Doug Smythies" <dsmythies@...us.net>
To: "'Artem Bityutskiy'" <artem.bityutskiy@...ux.intel.com>
Cc: "'LKML'" <linux-kernel@...r.kernel.org>,
"'Daniel Lezcano'" <daniel.lezcano@...aro.org>,
"'Christian Loehle'" <christian.loehle@....com>,
"'Aboorva Devarajan'" <aboorvad@...ux.ibm.com>,
"'Linux PM'" <linux-pm@...r.kernel.org>,
"'Rafael J. Wysocki'" <rjw@...ysocki.net>,
"Doug Smythies" <dsmythies@...us.net>
Subject: RE: [RFT][PATCH v1] cpuidle: teo: Avoid selecting deepest idle state over-eagerly
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.
Powered by blists - more mailing lists