From: Jesper Juhl <juhl@eisenstein.dk>
To: Chris Wedgwood <cw@f00f.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: How many pentium-3 processors does SMP support?
Date: Tue, 10 Jul 2001 16:10:32 +0000 [thread overview]
Message-ID: <3B4B28F8.49A6934A@eisenstein.dk> (raw)
In-Reply-To: <Pine.GSO.4.21.0107092315140.493-100000@faith.cs.utah.edu> <9ie450$d1p$1@cesium.transmeta.com> <20010711015128.E31799@weta.f00f.org>
Chris Wedgwood wrote:
>
> On Mon, Jul 09, 2001 at 10:34:24PM -0700, H. Peter Anvin wrote:
>
> It supports up to 32, if you can find a machine that has that
> many.
>
> I think 8-way is about as high as anything common goes to, maybe
> 16. The cpu array is declared 32 long, maybe this should be changed to
> 8 by default?
>
There are some machines (like the Compaq Proliant ML770 -
http://www.compaq.com/products/quickspecs/10698_div/10698_div.html) that
are actually sold as 32 way systems based on Pentium III Xeon CPU's, so
why not let the cpu array be able to handle that many CPU's by default
(maybe make a config option?)?
- Jesper Juhl
juhl@eisenstein.dk
next prev parent reply other threads:[~2001-07-10 14:10 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
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 [this message]
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=3B4B28F8.49A6934A@eisenstein.dk \
--to=juhl@eisenstein.dk \
--cc=cw@f00f.org \
--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