All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Hawkes" <hawkes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: sched-domains
Date: Thu, 18 Mar 2004 23:35:51 +0000	[thread overview]
Message-ID: <00db01c40d41$cf16f4c0$e3069aa3@PCJohn> (raw)
In-Reply-To: <20040317132100.106f62e7.akpm@osdl.org>

From: "Andrew Morton" <akpm@osdl.org>
...
> My question is: to what extent have the ia64 NUMA architectural people
> reviewed this code, and what is the risk that someone will come along in
> six months time saying we need to rip it all out?

I am generally happy with the architecture of sched-domains.  The big
advantage I see for large Altix-like NUMA platforms is that much of the
scheduler policy decisions are parameterized in sched_domain fields and are
more easily tuned on a per-architecture and per-platform basis.  In
particular, it is easy to define additional scheduler domains that are larger
than a single node and smaller than all the CPUs in the system, each domain
having its own parameterized characteristics of load-balance frequency, etc.

John Hawkes



      reply	other threads:[~2004-03-18 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 21:21 sched-domains Andrew Morton
2004-03-18 23:35 ` John Hawkes [this message]

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='00db01c40d41$cf16f4c0$e3069aa3@PCJohn' \
    --to=hawkes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.