From: Andi Kleen <ak@suse.de>
To: Dave Jones <davej@redhat.com>,
Nigel Cunningham <ncunningham@cyclades.com>,
Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: for_each_online_cpu broken ?
Date: Thu, 8 Dec 2005 07:30:09 +0100 [thread overview]
Message-ID: <20051208063009.GK11190@wotan.suse.de> (raw)
In-Reply-To: <20051208062844.GF28201@redhat.com>
On Thu, Dec 08, 2005 at 01:28:44AM -0500, Dave Jones wrote:
> On Thu, Dec 08, 2005 at 04:22:05PM +1000, Nigel Cunningham wrote:
>
> > > Yep, I noticed it offers a maximum of 6 cpus on my way.
> > > As a sidenote, seems kinda funny (and wasteful maybe?), doing this
> > > on a lot of hardware that isn't hotplug capable. (Whilst I could
> > > disable cpu hotplug in my local build, this isn't an answer for
> > > a generic distro kernel).
> >
> > Both suspend to disk (and suspend to ram?) implementations now depend on
> > hotplug_cpu to enable extra cpus, so there is at least one reason for
> > them to want hotplug support in a generic kernel.
>
> You mean suspend -> plug in a new cpu -> resume transitions ?
> That sounds *terrifying*.
No, they unplug all non BP CPUs before suspending.
It obviously doesn't require additional CPUs though.
-Andi
next prev parent reply other threads:[~2005-12-08 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 5:07 Dave Jones
2005-12-08 5:26 ` Andi Kleen
2005-12-08 5:33 ` Dave Jones
2005-12-08 5:38 ` David S. Miller
2005-12-08 6:12 ` Andi Kleen
2005-12-08 6:27 ` Dave Jones
2005-12-08 6:22 ` Nigel Cunningham
2005-12-08 6:28 ` Dave Jones
2005-12-08 6:30 ` Andi Kleen [this message]
2005-12-09 0:03 ` Nigel Cunningham
2005-12-08 6:30 ` Andi Kleen
2005-12-08 6:43 ` Dave Jones
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=20051208063009.GK11190@wotan.suse.de \
--to=ak@suse.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.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®