[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8UYtEepRT3xC8O/@gmail.com>
Date: Mon, 16 Jan 2023 10:28:20 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Daniel Bristot de Oliveira <bristot@...nel.org>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Valentin Schneider <vschneid@...hat.com>,
Joe Mario <jmario@...hat.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [PATCH] sched/idle: Make idle poll dynamic per-cpu
* Ingo Molnar <mingo@...nel.org> wrote:
> > Urgh, can we please make this a cpuidle governor thing or so? So that
> > we don't need to invent new interfaces and such.
>
> I think the desired property here would be to make this interface on top
> of pretty much any governor. Ie. have a governor, but also a way to drop
> any CPU into idle-poll, overriding that.
... with the goal of having the best governor for power efficiency by
default - but also the ability to drop a handful of CPUs into the highest
performance / lowest latency idle mode.
It's a special kind of nested policy, for workload exceptions.
Thanks,
Ingo
Powered by blists - more mailing lists