From: Frederic Weisbecker <fweisbec@gmail.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
gilad@benyossef.com, Len Brown <lenb@kernel.org>,
shli@kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: CPU isolation question again
Date: Wed, 4 Jul 2012 16:36:39 +0200 [thread overview]
Message-ID: <20120704143635.GE28294@somewhere> (raw)
In-Reply-To: <CAJRGBZyBGL97MAjBVBa5cKKsePtDFPiWqN4N-Lcw3V8qw35DTQ@mail.gmail.com>
On Wed, Jul 04, 2012 at 10:12:43PM +0800, Luming Yu wrote:
> On Wed, Jul 4, 2012 at 9:25 PM, Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > On Wed, Jul 04, 2012 at 08:42:29PM +0800, Luming Yu wrote:
> >> On Tue, Jul 3, 2012 at 7:28 PM, Frederic Weisbecker <fweisbec@gmail.com> wrote:
> >> > On Wed, Jun 27, 2012 at 09:22:09PM +0800, Luming Yu wrote:
> >> >> Hi there,
> >> >>
> >> >> I noticed some discussion about CPU isolation which points me to the
> >> >> patch set (https://lkml.org/lkml/2011/8/15/245). I'm currently
> >> >> preparing a RFC-patch-set to automatically pick up a few suitable CPUs
> >> >> to isolate then kick them out of service for a while. We need to
> >> >> balance between thermal & power management And overall system
> >> >> performance during this operation as much as possible. So
> >> >> software-cpu-online-offline interface could not be a good option to
> >> >> me. But to make sure I'm not blindly running on a dead-end path, I'd
> >> >> check with experts here to ensure it makes some sense to isolate CPUs
> >> >> to this level, and the idea also makes some sense, and the most
> >> >> important is it's not implemented yet.
> >> >
> >> > I don't understand what you are trying to do and how exactly. How do you
> >> > plan to do this isolation and how do you want to balance between thermal
> >> > and power?
> >>
> >> My question could be wrong as the question arose several weeks ago
> >> when I came across
> >> drivers/acpi/acpi_paid.c which looks like a real user who need to
> >> request system automatically
> >> pick up a few CPU to get them isolated and deactivated. Later on, I
> >> noticed tglx's cpu hot plug re-work.
> >> I realized we could reuse the interface to do isolation and deactivation work.
> >>
> >> Of cause, to pick up which ones to isolate and deactivate is another problem.
> >>
> >> cc'ed the author and ACPI maintainer of the driver as well as tglx.
> >
> > May be I'm confused because we both have our own definition of isolation.
> > I'm not sure what kind of CPU isolation you're looking for.
>
> At first, it needs not avaiable to scheduler. Then, it needs in
> deepest power saving mode.
> At last, it needs available to scheduler again on demand.
> Sounds very like a typical soft offline cpu, but needs to be low light weight.
I see. So indeed the latest developments made in CPU hotplug could make it a solution
for you.
next prev parent reply other threads:[~2012-07-04 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 13:22 CPU isolation question again Luming Yu
2012-07-03 11:28 ` Frederic Weisbecker
2012-07-04 12:42 ` Luming Yu
2012-07-04 13:25 ` Frederic Weisbecker
2012-07-04 14:12 ` Luming Yu
2012-07-04 14:36 ` Frederic Weisbecker [this message]
2012-07-10 9:37 ` Luming Yu
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=20120704143635.GE28294@somewhere \
--to=fweisbec@gmail.com \
--cc=gilad@benyossef.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=shli@kernel.org \
--cc=tglx@linutronix.de \
/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