public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org, John Hawkes <hawkes@sgi.com>
Subject: Re: [PATCH] add scheduler domains for ia64
Date: Fri, 20 Aug 2004 08:06:21 +0000	[thread overview]
Message-ID: <20040820080621.GA2310@elte.hu> (raw)
In-Reply-To: <200408192222.35512.jbarnes@engr.sgi.com>


* Jesse Barnes <jbarnes@engr.sgi.com> wrote:

> This patch adds some more NUMA specific logic to the creation of
> scheduler domains.  Domains spanning all CPUs in a large system are
> too large to schedule across efficiently, leading to livelocks and
> inordinate amounts of time being spent in scheduler routines.  With
> this patch applied, the node scheduling domains for NUMA platforms
> will only contain a specified number of nearby CPUs, based on the
> value of SD_NODES_PER_DOMAIN.  It also allows arches to override
> SD_NODE_INIT, which sets the domain scheduling parameters for each
> node's domain.  This is necessary especially for large systems.

looks good to me too.

Signed-off-by: Ingo Molnar <mingo@elte.hu>

	Ingo

      parent reply	other threads:[~2004-08-20  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 18:08 [PATCH] add scheduler domains for ia64 Jesse Barnes
2004-08-14  3:23 ` Nick Piggin
2004-08-14 20:52   ` Jesse Barnes
2004-08-15  0:54     ` Nick Piggin
2004-08-17 20:57       ` Jesse Barnes
2004-08-20  2:11         ` Nick Piggin
2004-08-20  2:22           ` Jesse Barnes
2004-08-20  6:28             ` Andrew Morton
2004-08-20 14:57               ` Jesse Barnes
2004-08-20  8:06             ` Ingo Molnar [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=20040820080621.GA2310@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=hawkes@sgi.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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