public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: cw@f00f.org (Chris Wedgwood)
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: How many pentium-3 processors does SMP support?
Date: Tue, 10 Jul 2001 16:12:00 +0200	[thread overview]
Message-ID: <200107101412.f6AEC0W06951@ns.caldera.de> (raw)
In-Reply-To: <20010711015128.E31799@weta.f00f.org>

In article <20010711015128.E31799@weta.f00f.org> you 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?

Why limit the user?  There are more than enough Linux system that have
more than 32 CPUs (SGI, DEC, Sun).

Making it a per-architecture value or even a config option make a lot
more sense.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  reply	other threads:[~2001-07-10 14:12 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 [this message]
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
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=200107101412.f6AEC0W06951@ns.caldera.de \
    --to=hch@ns.caldera.de \
    --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