From: William Lee Irwin III <wli@holomorphy.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] CPUSET Proposal
Date: Thu, 25 Sep 2003 06:02:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106447093307460@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106442121824485@msgid-missing>
On Wed, 24 Sep 2003 09:30:44 -0700, Stephen Hemminger <shemminger@osdl.org> said:
Stephen> Looks good, but you aren't likely to get much acceptance or
Stephen> testing if it only works on ia64. You need to make a
Stephen> version for i386 as well.
On Wed, Sep 24, 2003 at 10:02:35AM -0700, David Mosberger wrote:
> Is this true for >8-way machines?
x86's architectural limitations are 64x for serial APIC -based machines
(e.g. NUMA-Q) and 255x for xAPIC -based machines (no known extant > 32x
machines, apparently some kind of non-architectural regression), where
the non-power-of-two number of cpus is due to the broadcast ID reserved
from an 8-bit interrupt controller ID space. A likely explanation for
the current xAPIC limitations is the recommended (publicly documented)
physical APIC ID enumeration scheme breaking down for > 32x.
Custom interrupt controllers may exceed these limits, but I don't know
of any that have actually been made use of to do so. Though it sucks
and very, very badly, x86 is not limited to anything like 8x.
-- wli
next prev parent reply other threads:[~2003-09-25 6:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 16:30 [Lse-tech] CPUSET Proposal Stephen Hemminger
2003-09-24 17:02 ` David Mosberger
2003-09-24 19:32 ` Gerrit Huizenga
2003-09-24 21:42 ` Paul Jackson
2003-09-25 5:40 ` Paul Jackson
2003-09-25 5:44 ` Paul Jackson
2003-09-25 6:02 ` William Lee Irwin III [this message]
2003-09-25 6:57 ` David Mosberger
2003-09-25 7:07 ` David Mosberger
2003-09-25 7:08 ` William Lee Irwin III
2003-09-25 7:14 ` William Lee Irwin III
2003-09-25 9:04 ` Dave Hansen
2003-09-25 18:07 ` Shailabh Nagar
2003-09-25 18:08 ` William Lee Irwin III
2003-09-25 20:50 ` Shailabh Nagar
2003-09-26 7:36 ` Simon Derr
2003-09-26 9:58 ` Paul Jackson
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=marc-linux-ia64-106447093307460@msgid-missing \
--to=wli@holomorphy.com \
--cc=linux-ia64@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.