From: Ashok Raj <ashok.raj@intel.com>
To: Andi Kleen <ak@muc.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Cc: discuss@x86-64.org
Cc: Rusty Russell <rusty@rustycorp.com.au>
Cc: Srivattsa Vaddagiri <vatsa@in.ibm.com>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Subject: [patch 0/5] x86_64 CPU hotplug patch series.
Date: Thu, 02 Jun 2005 05:57:55 -0700 [thread overview]
Message-ID: <20050602125754.993470000@araj-em64t> (raw)
Hi,
Attached are the set of patches to support x86-64 logical cpu hot-add/remove.
Special thanks to Andi for painfully reviewing some interim versions.
It seems to hold tight for overnight stress tests with make -j's and
hotplug happening in parallel.
Andrew: Could you help test staging in -mm so we can get some wider testing
from those interested.
*Sore Point*: Andi doesnt agree with one patch that removes ipi-broadcast
and uses only online map cpus receive IPI's. This is much simpler approach to
handle instead of trying to remove the ill effects of IPI broadcast to CPUs in
offline state.
Initial concern from Andi was IPI performance, but some primitive test with a
good number of samples doesnt seem to indicate any degration at all, infact the
results seem identical. (Barring any operator errors :-( ).
It would be nice to hear other opinions as well, hopefuly we can close on
what what the right approach in this case. Link to an earlier discussion
on the topic.
http://marc.theaimsgroup.com/?l=linux-kernel&m=111695485610434&w=2
Rusty (who has been hiding somewhere in the woods these days :-)), could
you suggest something...
Cheers,
Ashok Raj
next reply other threads:[~2005-06-02 13:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 12:57 Ashok Raj [this message]
2005-06-02 12:57 ` [patch 1/5] x86_64: Change init sections for CPU hotplug support Ashok Raj
2005-06-02 20:14 ` Zwane Mwaikambo
2005-06-02 23:19 ` Ashok Raj
2005-06-02 12:57 ` [patch 2/5] x86_64: " Ashok Raj
2005-06-02 20:19 ` Zwane Mwaikambo
2005-06-02 23:33 ` Ashok Raj
2005-06-02 23:45 ` Zwane Mwaikambo
2005-06-03 0:08 ` Ashok Raj
2005-06-03 2:01 ` Shaohua Li
2005-06-03 14:25 ` Ashok Raj
2005-06-02 12:57 ` [patch 3/5] x86_64: CPU hotplug sibling map cleanup Ashok Raj
2005-06-02 12:57 ` [patch 4/5] x86_64: Dont use broadcast shortcut to make it cpu hotplug safe Ashok Raj
2005-06-02 12:58 ` [patch 5/5] x86_64: Provide ability to choose using shortcuts for IPI in flat mode Ashok Raj
2005-06-02 20:10 ` Zwane Mwaikambo
2005-06-02 23:15 ` Ashok Raj
2005-06-02 20:25 ` [patch 0/5] x86_64 CPU hotplug patch series Zwane Mwaikambo
2005-06-03 16:35 ` Andi Kleen
2005-06-03 17:15 ` Ashok Raj
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=20050602125754.993470000@araj-em64t \
--to=ashok.raj@intel.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/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®