From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: Christoph Hellwig <hch@ns.caldera.de>,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: How many pentium-3 processors does SMP support?
Date: Tue, 10 Jul 2001 08:26:09 -0700 [thread overview]
Message-ID: <3B4B1E91.A7D75608@osdlab.org> (raw)
In-Reply-To: <20010711022509.C31966@weta.f00f.org>
Chris Wedgwood wrote:
>
> On Tue, Jul 10, 2001 at 04:19:43PM +0200, Christoph Hellwig wrote:
>
> The number of CPUs is currently globally limited to 32 by NR_CPUS in
> include/linux/threads.h.
>
> Really?
>
> <pause>
>
> Ah, so it is... yes, making this architecture dependant might be a
> good idea. Large PPC and MIPS boxen need to adjust this already. Also,
> someone did a starfire port, I think that had 64 processors, not sure.
>
> You can. But you cannot buy 32-processor PII (-Xeon) systems that are
> supported by Linux.
>
> What is the limit here? The 8/16 way SE chipsets?
>
> > In anyone from Compaq is reading this, you should send me a 32-way
> > Xeon ASAP just to prove they really work :)
>
> It doesn't.
>
> Oh, then they definately need to send me one.
>
> Are these not MP1.4 based? Something different?
>
> --cw
For IA32/i386/x86:
The Linus-kernel only supports a maximum of 15 Pentium IIIs
due to APIC addressing (4 bits, with 0xf meaning "broadcast").
Pentium 4 uses 0xff for broadcast, so lots more of them can
be supported (when you can find a P-4 MP server).
I have heard of some IBM/Sequent patches that modify the
logical vs. physical APIC addressing scheme to make 16-way
systems work.
--
~Randy
next prev parent reply other threads:[~2001-07-10 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 5:17 How many pentium-3 processors does SMP support? Xinwei Xue
2001-07-10 5:34 ` H. Peter Anvin
2001-07-10 13:51 ` Chris Wedgwood
2001-07-10 14:12 ` Christoph Hellwig
2001-07-10 14:16 ` Chris Wedgwood
2001-07-10 14:19 ` Christoph Hellwig
2001-07-10 14:25 ` Chris Wedgwood
2001-07-10 14:32 ` Christoph Hellwig
2001-07-10 14:36 ` Chris Wedgwood
2001-07-10 15:26 ` Randy.Dunlap [this message]
2001-07-10 15:50 ` Chris Wedgwood
2001-07-10 15:57 ` Christoph Hellwig
2001-07-10 16:29 ` Ralf Baechle
2001-07-10 16:10 ` Jesper Juhl
2001-07-10 14:30 ` Chris Wedgwood
2001-07-10 14:43 ` Jesper Juhl
[not found] <85256A85.007E98E0.00@D51MTA03.pok.ibm.com>
2001-07-10 23:24 ` Martin J. Bligh
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=3B4B1E91.A7D75608@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=cw@f00f.org \
--cc=hch@ns.caldera.de \
--cc=hpa@zytor.com \
--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