From: Jack Steiner <steiner@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: SLIT and IO-only nodes
Date: Fri, 19 Nov 2004 15:18:35 -0600 [thread overview]
Message-ID: <20041119211835.GA21349@sgi.com> (raw)
An SGI Altix SSI system consists of a collection of nodes connected via a
high speed interconnect. Nodes come in several flavors:
- memory, IO and cpus
- memory & cpus
- memory only
- IO only
- (other combinations don't exist yet)
The first 2 types of nodes are typical.
You can think of the last 2 types of nodes as nodes that have been
partially depopulated.
We need to describe all these nodes in the SLIT table.
For example, when allocating memory on a memory-only node,
knowing the distance to the node is important.
When assigning cpus to service interrupts for IO nodes or when creating
driver memory structures for devices on IO nodes, it is important
to use the nearest node that has cpus & memory.
On IA64, memory-only nodes are described in the SRAT, have a proximity
domain number, NIDs, and appear in the SLIT. (ie., we don't have
a problem with memory-only nodes).
However, IO-only nodes (AFAICT) cannot be described in the SLIT.
The SLIT is indexed by proximity_domain_number (PXM).
Currently, there is no SRAT entry for IO-only nodes. These nodes do not
appear in the SLIT. It would seem that a new ACPI table is
needed for IO-only nodes. The SRAT would describe the node & identify
the IO buses that are attached to the node. I think this would give us
what we need.
Before I start digging into the ACPI spec, has anyone already addressed
this problem? Is this the right approach to take to solve the problem?
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
reply other threads:[~2004-11-19 22:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041119211835.GA21349@sgi.com \
--to=steiner@sgi.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