From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
linux-kernel@vger.kernel.org, John Hawkes <hawkes@sgi.com>
Subject: Re: [RFC] Patch for isolated scheduler domains
Date: Sat, 24 Jul 2004 11:40:28 -0400 [thread overview]
Message-ID: <200407241140.29453.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <4101F2ED.3050208@yahoo.com.au>
On Saturday, July 24, 2004 1:26 am, Nick Piggin wrote:
> You might have the theoretical problem of ending up with more than
> one disjoint top level domain (ie. no overlap, basically partitioning
> the CPUs).
Yes, we'll have several disjoint per-node cpu spans for a large system, but
nearby nodes *will* overlap with more distant nodes than any given node, so I
think we're covered, unless I'm misunderstanding something.
> No doubt you could come up with something provably correct, however
> it might just be good enough to examine the end result and check that
> it is good. At least while you test different configurations.
Right. And ultimately, I think we'll want the hierarchy I mentioned in the
comments, that'll cover us a little better I think.
Jesse
next prev parent reply other threads:[~2004-07-24 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 16:41 Dimitri Sivanich
2004-07-22 17:54 ` Ingo Molnar
2004-07-23 3:27 ` Nick Piggin
2004-07-23 4:13 ` Dimitri Sivanich
2004-07-23 4:29 ` Nick Piggin
2004-07-22 19:34 ` Paul Jackson
2004-07-23 20:03 ` Jesse Barnes
2004-07-24 5:26 ` Nick Piggin
2004-07-24 15:40 ` Jesse Barnes [this message]
2004-07-25 4:26 ` 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=200407241140.29453.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=hawkes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=sivanich@sgi.com \
/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
all inboxes | Powered by JetHome®