public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
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 18:29:36 +0200	[thread overview]
Message-ID: <20010710182936.A31341@bacchus.dhis.org> (raw)
In-Reply-To: <20010710161943.A7785@caldera.de> <20010711022509.C31966@weta.f00f.org>
In-Reply-To: <20010711022509.C31966@weta.f00f.org>; from cw@f00f.org on Wed, Jul 11, 2001 at 02:25:09AM +1200

On Wed, Jul 11, 2001 at 02:25:09AM +1200, Chris Wedgwood wrote:

>     The number of CPUs is currently globally limited to 32 by NR_CPUS in
>     include/linux/threads.h.
> 
> Really?
> 
> <pause>

A define which can easily be changed.

> 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.

The next limit are bitfields for processors in a number of places.  They're
stored in unsigned long variables, so this limits the kernel to 32
processors on 32-bit machines and 64 on 64-bit machines.  Kanoj once
fixed that and we had Linux booting on a 128p Origin but I'm not sure
if those fixes went back to Linus.  Once this is fixed there is a number
of arrays with NR_CPUS elements in struct task_struct.  Once you reach
an estimated number of 200-300 processors (for 16kb kernel stacks) those
make task_struct that large that the kernel stack may overflow.  I
haven't really researched all the gotchas that may cause problems with
the kernel when going to machines of more than 128 processors.

  Ralf

  parent reply	other threads:[~2001-07-10 19:51 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 [this message]
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=20010710182936.A31341@bacchus.dhis.org \
    --to=ralf@uni-koblenz.de \
    --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