From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
William Lee Irwin III <wli@holomorphy.com>,
"Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: Christoph Hellwig <hch@infradead.org>,
James Cleverdon <jamesclv@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>,
"Van Maren, Kevin" <kevin.vanmaren@UNISYS.com>,
Andi Kleen <ak@suse.de>, Hubert Mantel <mantel@suse.de>,
"Kamble, Nitin A" <nitin.a.kamble@intel.com>
Subject: RE: [PATCH][2.4] generic cluster APIC support for systems with m ore than 8 CPUs
Date: Sat, 21 Dec 2002 20:05:18 -0800 [thread overview]
Message-ID: <6470000.1040529916@titus> (raw)
In-Reply-To: <C8C38546F90ABF408A5961FC01FDBF1912E1AF@fmsmsx405.fm.intel.com>
> Yes, our feeling it is possible to handle all non-NUMAQ systems pretty
> generically in terms of APIC setup and interrupt routing. We can use
> either logical clustered or physical destination modes. But for NUMAQ
> systems, interrupt routing has to know about the local nodes and have
> necessary logic to do the routing withing local node.
NUMA-Q doesn't have to know about the local nodes. I set it up to use
physical delivery broadcast, which is a node-local broadcast ... gave
me NUMA affinity for free. I could also use logical clustered (p3 style)
addressing, and work out all the node locality, but I don't see the point.
M.
next prev parent reply other threads:[~2002-12-22 3:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 4:00 [PATCH][2.4] generic cluster APIC support for systems with m ore than 8 CPUs Pallipadi, Venkatesh
2002-12-22 4:05 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 18:58 Protasevich, Natalie
2003-01-08 14:53 ` Alan Cox
2002-12-26 2:18 Van Maren, Kevin
2002-12-27 23:38 ` Alan Cox
2002-12-26 1:14 Protasevich, Natalie
2002-12-27 23:39 ` Alan Cox
2002-12-23 7:29 Kamble, Nitin A
2002-12-23 7:52 ` Martin J. Bligh
2002-12-23 9:46 ` Zwane Mwaikambo
2002-12-23 15:30 ` Martin J. Bligh
[not found] <3FAD1088D4556046AEC48D80B47B478C1AEC75@usslc-exch-4.slc.unisys. com>
2002-12-22 20:41 ` Protasevich, Natalie
2002-12-22 20:52 ` Martin J. Bligh
2002-12-22 6:19 Pallipadi, Venkatesh
2002-12-22 6:39 ` William Lee Irwin III
2002-12-22 17:21 ` Martin J. Bligh
2002-12-22 17:23 ` Martin J. Bligh
2002-12-20 22:57 Protasevich, Natalie
2002-12-20 23:33 ` William Lee Irwin III
2002-12-25 21:41 ` Alan Cox
[not found] <3FAD1088D4556046AEC48D80B47B478C0101F55D@usslc-exch-4.slc.unisy s.com>
2002-12-20 15:46 ` Van Maren, Kevin
2002-12-20 16:30 ` Martin J. Bligh
2002-12-20 17:16 ` William Lee Irwin III
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=6470000.1040529916@titus \
--to=mbligh@aracnet.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=ak@suse.de \
--cc=asit.k.mallick@intel.com \
--cc=hch@infradead.org \
--cc=jamesclv@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.vanmaren@UNISYS.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mantel@suse.de \
--cc=nitin.a.kamble@intel.com \
--cc=sunil.saxena@intel.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).