From: William Lee Irwin III <wli@holomorphy.com>
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: "'Mika Penttil?'" <mika.penttila@kolumbus.fi>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2][2.5]Unisys ES7000 platform subarch
Date: Wed, 11 Jun 2003 09:52:38 -0700 [thread overview]
Message-ID: <20030611165238.GF26348@holomorphy.com> (raw)
In-Reply-To: <3FAD1088D4556046AEC48D80B47B478C022BDA78@usslc-exch-4.slc.unisys.com>
On Wed, Jun 11, 2003 at 11:40:05AM -0500, Protasevich, Natalie wrote:
> Clustering on ES7000 follows Intel guidelines, but not quite fall into
> certain cluster model category. According to Intel book, cluster can be flat
> (on the same bus) or hierarchical (physically separate bus segments). Flat
> cluster uses serial bus messaging (like on xAPIC systems) and can support 15
> agents. On both APIC models that ES7000 utilizes, it can support 32
> processors (with xAPICs, 64 hypothreaded P4's, if only OS could support
> that). It has special arrangement for the APIC buses and corresponding
> numbering for APICs, which reflects its topological nature, so the
> conventional APIC cluster numbering schema won't work. Due to those
> differences, our clusters are not that "flat", and we call it "physical",
> and "logical" really means "hierarchical". I think, our cluster model names
> came from some previous distributions that implemented both models, I swear
> I didn't invent it myself. They just worked for our case.
This nomenclature has also been used by other large i386 system vendors
besides Unisys, e.g. Sequent.
-- wli
next prev parent reply other threads:[~2003-06-11 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 16:40 [PATCH 2/2][2.5]Unisys ES7000 platform subarch Protasevich, Natalie
2003-06-11 16:52 ` William Lee Irwin III [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-11 13:42 Protasevich, Natalie
2003-06-11 15:56 ` Mika Penttilä
2003-06-11 21:52 ` James Cleverdon
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=20030611165238.GF26348@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.penttila@kolumbus.fi \
/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