From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Allow to change SD_NODES_PER_DOMAIN at configuration or boot time
Date: Thu, 17 Feb 2005 00:13:10 +0000 [thread overview]
Message-ID: <200502161613.11170.jbarnes@sgi.com> (raw)
In-Reply-To: <42138013.3060909@bull.net>
On Wednesday, February 16, 2005 4:08 pm, Luck, Tony wrote:
> I guess I still don't understand how defining the number of
> nodes per domain gets the *right* nodes assigned to a domain.
> Does this rely on node discovery code assigning logical node
> numbers in such a way that nodes 0, 1, 2, 3 belong to one
> domain, and nodes 4, 5, 6, 7 belong to the next domain (for
> a system where SD_NODES_PER_DOMAIN=4)? What if we have a
> system where node numbers are effectively randomly assigned
> by firmware at power-on? Then nodes 0, 3, 6, 7 might make up
> a super-node, but we'll create a couple of domains that have
> a jumbled mix of nodes from each super-node.
It uses the SLIT table to put a cluster of SD_NODES_PER_DOMAIN nodes into a
sched domain. So if SD_NODES_PER_DOMAIN is 4, node 0 will be in a domain
with the three nodes closest to node 0, which could be node 9, 15, and 2 for
all we know...
> That's why I asked whether we need to parse the SLIT to determine
> how many nodes belong to a domain ... but also to find out
> which nodes are in which domain.
I don't think the SLIT gives us enough info to determine the best grouping of
nodes, but it depends on how the various firmwares build it--some may.
Jesse
next prev parent reply other threads:[~2005-02-17 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 17:17 Allow to change SD_NODES_PER_DOMAIN at configuration or boot time Xavier Bru
2005-02-17 0:08 ` Luck, Tony
2005-02-17 0:13 ` Jesse Barnes [this message]
2005-02-17 0:28 ` Allow to change SD_NODES_PER_DOMAIN at configuration or boot Nick Piggin
2005-02-17 1:07 ` Allow to change SD_NODES_PER_DOMAIN at configuration or boot time Luck, Tony
2005-02-17 1:24 ` Jesse Barnes
2005-02-17 11:05 ` Allow to change SD_NODES_PER_DOMAIN at configuration or boot Xavier Bru
2005-02-17 16:33 ` Nick Piggin
2005-02-24 7:39 ` Nick Piggin
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=200502161613.11170.jbarnes@sgi.com \
--to=jbarnes@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox