From: "Martin J. Bligh" <mbligh@aracnet.com>
To: William Lee Irwin III <wli@holomorphy.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
"Van Maren, Kevin" <kevin.vanmaren@unisys.com>,
Christoph Hellwig <hch@infradead.org>,
James Cleverdon <jamesclv@us.ibm.com>,
John Stultz <johnstul@us.ibm.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Protasevich, Natalie" <Natalie.Protasevich@unisys.com>
Subject: Re: [PATCH][2.4] generic support for systems with more than 8 CPUs (2/2)
Date: Sun, 22 Dec 2002 09:47:28 -0800 [thread overview]
Message-ID: <36680000.1040579247@titus> (raw)
In-Reply-To: <20021222121717.GH25000@holomorphy.com>
> IIRC NUMA-Q can be dynamically detected at boot by means of an MP OEM
> table's presence, in particular if there's a matching string in the 8B
> OEM record in the OEM table, with a value of "IBM NUMA" IIRC. This is
> probably a line or two's worth of change to mpparse.c and declaring a
> variable for clustered_apic_mode. If it were difficult to detect, I
> wouldn't have suggested implementing it (though do so at your leisure). =)
>
> I still think this is 2.5 material + backport once it gets testing there.
I think there are still some things around that are switched on #defines
for NUMA-Q. Also older machines will probably say Sequent instead of IBM
in the OEM table. Would need some testing ...
M.
next prev parent reply other threads:[~2002-12-22 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 6:59 [PATCH][2.4] generic support for systems with more than 8 CPUs (2/2) Pallipadi, Venkatesh
2002-12-22 12:17 ` William Lee Irwin III
2002-12-22 17:47 ` Martin J. Bligh [this message]
2002-12-22 22:23 ` William Lee Irwin III
2002-12-22 17:43 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 1:36 Pallipadi, Venkatesh
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=36680000.1040579247@titus \
--to=mbligh@aracnet.com \
--cc=Natalie.Protasevich@unisys.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.