All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	John Hawkes <hawkes@sgi.com>,
	Martin Hicks <mort@wildopensource.com>,
	Shai Fultheim <Shai@ScaleMP.com>
Subject: Re: [PATCH] reduce inter-node balancing frequency
Date: 18 Jul 2004 09:12:13 -0400	[thread overview]
Message-ID: <yq08ydhsbma.fsf@wildopensource.com> (raw)
In-Reply-To: <200407151829.20069.jbarnes@engr.sgi.com>

>>>>> "Jesse" == Jesse Barnes <jbarnes@engr.sgi.com> writes:

Jesse> Nick, we've had this patch floating around for awhile now and
Jesse> I'm wondering what you think.  It's needed to boot systems with
Jesse> lots (e.g. 256) nodes, but could probably be done another way.
Jesse> Do you think we should create a scheduler domain for every 64
Jesse> nodes or something?  Any other NUMA folks have thoughts about
Jesse> these values?

vSMP could use something like this as well. I think Martin Hicks
already did an arch-aware patch for setting these things.

Jes

      parent reply	other threads:[~2004-07-18 13:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15 22:29 [PATCH] reduce inter-node balancing frequency Jesse Barnes
2004-07-16  0:14 ` Martin J. Bligh
2004-07-16  0:38   ` Jesse Barnes
2004-07-16  1:48     ` Nick Piggin
2004-07-16  1:58       ` Jesse Barnes
2004-07-16  5:40         ` Martin J. Bligh
2004-07-16  5:53           ` Nick Piggin
2004-07-16 14:45             ` Jesse Barnes
2004-07-16 15:04               ` Chris Wedgwood
2004-07-16 15:30                 ` Jesse Barnes
2004-07-17  3:00               ` Nick Piggin
2004-07-17 16:44                 ` Jesse Barnes
2004-07-16 14:42           ` Jesse Barnes
2004-07-18 13:12 ` Jes Sorensen [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=yq08ydhsbma.fsf@wildopensource.com \
    --to=jes@wildopensource.com \
    --cc=Shai@ScaleMP.com \
    --cc=hawkes@sgi.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mort@wildopensource.com \
    --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 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.