All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Colin Coe <colin@coesta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Max CPUs on x86_64 under 2.6.x
Date: Mon, 3 Jan 2005 14:15:16 -0800	[thread overview]
Message-ID: <20050103221516.GV29332@holomorphy.com> (raw)
In-Reply-To: <44438.202.154.120.74.1104760841.squirrel@www.coesta.com>

On Mon, Jan 03, 2005 at 10:00:41PM +0800, Colin Coe wrote:
> Why is the number of CPUs on the x86_64 architecture only 8 but under i386
> it is 255?
> I've searched the list archives and Google but can't find an answer.

i386 machines have had interrupt controllers and "large scale" systems
(to the extent that 32-bit machines can be so) developed for some time.
x86-64 machines are newer, and it is the maintainer's preference to
start with a fresh codebase for the APIC.

So what you see is not a reflection of x86-64's capabilities, but
rather, of the newness of the architecture and the codebase's desire
to be "legacy-free" in manners that don't pose the threat of causing
immediate problems.

It is not now limiting the capabilities of x86-64 machines because
x86-64 machines of 64 cpus or larger have yet to be produced. For the
record, I'm unaware of SSI i386 machines larger than 64 processors.
255 represents nothing more than a theoretical limit of hardware
capabilities, and no i386 machine larger than 64 processors has ever
been constructed to the best of my knowledge.


-- wli

  reply	other threads:[~2005-01-03 22:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-03 14:00 Max CPUs on x86_64 under 2.6.x Colin Coe
2005-01-03 22:15 ` William Lee Irwin III [this message]
2005-01-04  0:17   ` Colin Coe
2005-01-04  2:12     ` William Lee Irwin III
2005-01-04  0:34 ` Andi Kleen
2005-01-04  2:20   ` William Lee Irwin III
2005-01-04 11:09     ` Andi Kleen

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=20050103221516.GV29332@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=colin@coesta.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 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.