From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
John Hawkes <hawkes@sgi.com>
Subject: Re: [PATCH] reduce inter-node balancing frequency
Date: Thu, 15 Jul 2004 17:14:40 -0700 [thread overview]
Message-ID: <46970000.1089936880@flay> (raw)
In-Reply-To: <200407151829.20069.jbarnes@engr.sgi.com>
> Nick, we've had this patch floating around for awhile now and I'm wondering
> what you think. It's needed to boot systems with lots (e.g. 256) nodes, but
> could probably be done another way. Do you think we should create a
> scheduler domain for every 64 nodes or something?
I think that'd make a lot of sense ...
> Any other NUMA folks have thoughts about these values?
Yeah, change them in arch specific code, not in the global stuff ;-)
But seeing as they're dependant (for you) on machine size, as well as
arch type, you probably need to do something cleverer in arch_init_sched_domain
But the big bugaboo is arch-specific vs general ... we need to break
opteron vs i386 vs ia64 out from each other ... they all need different
coefficients.
If you were going to be really fancy, we could do it in common code off
the topology stuff ... but for now, I think it's easier to just set 'em
per arch ...
M.
next prev parent reply other threads:[~2004-07-16 0:15 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 [this message]
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
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=46970000.1089936880@flay \
--to=mbligh@aracnet.com \
--cc=hawkes@sgi.com \
--cc=jbarnes@engr.sgi.com \
--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