From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Joe Mario <jmario@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] sched/idle: Make idle poll dynamic per-cpu
Date: Mon, 16 Jan 2023 11:06:50 +0100 [thread overview]
Message-ID: <3cd68923-660b-42d9-2fce-4cf5f9369d18@redhat.com> (raw)
In-Reply-To: <Y8UYtEepRT3xC8O/@gmail.com>
On 1/16/23 10:28, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@kernel.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.
Yep, it is for the (extreme, but existing) case in which the user wants to skip idle driver
machinery (and overheads involved).
People use idle poll on high-frequency trading or to avoid scheduling out a vCPU,
but as the systems are becoming more dynamic (and shared), having this option dynamic
and per-cpu is useful...
-- Daniel
> Thanks,
>
> Ingo
>
next prev parent reply other threads:[~2023-01-16 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 16:24 Daniel Bristot de Oliveira
2023-01-15 9:15 ` Ingo Molnar
2023-01-17 11:20 ` Daniel Bristot de Oliveira
2023-01-16 1:43 ` Chen Yu
2023-01-16 8:53 ` Peter Zijlstra
2023-01-16 9:02 ` Ingo Molnar
2023-01-16 9:28 ` Ingo Molnar
2023-01-16 9:51 ` Vincent Guittot
2023-01-16 10:11 ` Daniel Bristot de Oliveira
2023-01-16 10:06 ` Daniel Bristot de Oliveira [this message]
2023-01-16 11:54 ` Peter Zijlstra
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=3cd68923-660b-42d9-2fce-4cf5f9369d18@redhat.com \
--to=bristot@redhat.com \
--cc=bristot@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jmario@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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
all inboxes | Powered by JetHome®