public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jesse Barnes <jbarnes@engr.sgi.com>
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 15:26:05 +1000	[thread overview]
Message-ID: <4101F2ED.3050208@yahoo.com.au> (raw)
In-Reply-To: <200407231603.09055.jbarnes@engr.sgi.com>

Jesse Barnes wrote:
> On Thursday, July 22, 2004 12:41 pm, Dimitri Sivanich wrote:
> 
>>I'm interested in implementing something I'll call isolated sched domains
>>for single cpus (to minimize the latencies involved when doing things like
>>load balancing on certain select cpus) on IA64.
> 
> 
> And here's what I had in mind for restricting the CPU span of a given node's 
> domain.  I haven't even compiled it though, so it probably won't work.  I'm 
> just posting it for comments.
> 
> I think the code can be reused for a hierarchical system too, by simply 
> looping in sched_domain_node_span with a few different values of SD_MAX_NODE.
> 
> Any thoughts?
> 

Yeah that is like what I had in mind.

You might have the theoretical problem of ending up with more than
one disjoint top level domain (ie. no overlap, basically partitioning
the CPUs).

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.

  reply	other threads:[~2004-07-24  5:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 16:41 [RFC] Patch for isolated scheduler domains 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 [this message]
2004-07-24 15:40     ` Jesse Barnes
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=4101F2ED.3050208@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=hawkes@sgi.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --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