From: Matthew Wilcox <matthew@wil.cx>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] top level scheduler domain for ia64
Date: Mon, 01 Nov 2004 17:16:49 +0000 [thread overview]
Message-ID: <20041101171649.GT8958@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200410191427.27336.jbarnes@engr.sgi.com>
On Mon, Nov 01, 2004 at 09:07:32AM -0800, Jesse Barnes wrote:
> If I understand you right, you don't want a top level domain for your 32 way
> systems, but you *do* want the node domains to span the whole thing. Is that
> right?
>
> If so, you could do something like this I think?
>
> if (numnodes <= SMALL_SYSTEM_THRESHOLD) {
> SD_NODES_PER_DOMAIN = numnodes;
> build_node_domains(); /* each one spans the system */
> } else {
> SD_NODES_PER_DOMAIN = 4; /* or whatever */
> build_node_domains(); /* only spans nearby nodes */
> build_top_level_domain(); /* whole system, infrequently balanced */
> }
>
> Would that address your concerns?
Doesn't sound like a great idea. HP's already shipping 128-way Superdome
IA-64 systems, and they'll want to be set up rather differently from the
Altix systems. I think this code needs to be autotuning so it doesn't
need to be touched whenever a vendor releases a new configuration (I
think I heard that NASA's Altixes had a custom CPU brick with twice the
CPUs in it?)
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-11-01 17:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 21:27 [PATCH] top level scheduler domain for ia64 Jesse Barnes
2004-10-20 0:02 ` Nick Piggin
2004-10-20 17:48 ` Luck, Tony
2004-10-20 18:02 ` Nick Piggin
2004-10-20 18:03 ` Jesse Barnes
2004-10-21 14:11 ` Xavier Bru
2004-10-21 14:34 ` Nick Piggin
2004-10-28 9:29 ` Takayoshi Kochi
2004-10-28 15:26 ` Jesse Barnes
2004-11-01 6:35 ` Takayoshi Kochi
2004-11-01 17:07 ` Jesse Barnes
2004-11-01 17:16 ` Matthew Wilcox [this message]
2004-11-01 18:36 ` Jesse Barnes
2004-11-01 18:53 ` Luck, Tony
2004-11-01 19:02 ` Jesse Barnes
2004-11-01 19:45 ` Luck, Tony
2004-11-01 22:39 ` Jesse Barnes
2004-11-02 0:12 ` Zou, Nanhai
2004-11-02 7:36 ` Takayoshi Kochi
2004-11-02 8:48 ` Gerald Pfeifer
2004-11-02 9:31 ` Takayoshi Kochi
2004-11-02 21:31 ` Luck, Tony
2004-11-03 6:15 ` Takayoshi Kochi
2004-11-03 16:22 ` Jesse Barnes
2004-11-03 16:57 ` Luck, Tony
2004-11-03 17:04 ` Jesse Barnes
2004-11-08 17:31 ` John Hawkes
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=20041101171649.GT8958@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--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