From: Rusty Russell <rusty@rustcorp.com.au>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: linux-kernel@vger.kernel.org, ralf@gnu.org, rhw@memalpha.cx,
mingo@redhat.com, paulus@samba.org, anton@samba.org,
schwidefsky@de.ibm.com, bh@sgi.com, davem@redhat.com, ak@suse.de,
torvalds@transmeta.com
Subject: Re: Hotplug CPU Boot Changes: BEWARE
Date: Mon, 10 Jun 2002 17:05:16 +1000 [thread overview]
Message-ID: <E17HJEs-00061l-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "07 Jun 2002 08:51:32 CST." <m1elfjw39n.fsf@frodo.biederman.org>
In message <m1elfjw39n.fsf@frodo.biederman.org> you write:
> But for the latter something just a little more than minimal hacks
> must be implemented. But dynamic cpu enable/disable is definitely
> worth it.
Perhaps I didn't make myself clear: hotplugging does not neccessarily
mean physically removing or adding the CPU. And as to whether they
offer full support, or stub support, architectures can decide that for
themselves, as they need. It's not my call.
I don't know how much of a win it is to disable HT on cpus, but I can
tell you that adding & subtracting CPUs is a fairly heavy-weight
operation in this design (I don't think we really want to lock around
every cpu iteration).
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-06-10 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 10:40 Rusty Russell
2002-06-07 14:51 ` Eric W. Biederman
2002-06-02 16:22 ` Pavel Machek
2002-06-08 1:55 ` Keith Owens
2002-06-10 7:05 ` Rusty Russell [this message]
2002-06-10 13:43 ` Eric W. Biederman
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=E17HJEs-00061l-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=bh@sgi.com \
--cc=davem@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=ralf@gnu.org \
--cc=rhw@memalpha.cx \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@transmeta.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®