From: Jesse Barnes <jbarnes@engr.sgi.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
John Hawkes <hawkes@sgi.com>
Subject: Re: [PATCH] reduce inter-node balancing frequency
Date: Fri, 16 Jul 2004 10:42:39 -0400 [thread overview]
Message-ID: <200407161042.39748.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <2700000.1089956404@[10.10.2.4]>
On Friday, July 16, 2004 1:40 am, Martin J. Bligh wrote:
> Arch code. Arch code. Arch code ;-) Or at least base it of nr_cpus or
> numnodes. Seriously ... a 2x or 4x opteron obviously needs different
> parameters from a 16x x440 or a 512x SGI box ... why we have a flexible
> infrastructure that can stand on its head and do backflips, and then
> we don't use it at all is a mystery to me ;-)
>
> I'd even go so far as to suggest there should be NO default settings for
> NUMA, only in arch code - that'd make people actually think about it.
> If there are, they should be based off the topo infrastructure, not static
> values.
Yep, no arguments here. I agree about not having default NUMA settings too,
having them only in arch code would be best. At least until we have a few
NUMA architectures using this stuff, then we can refactor out the common code
if it makes sense later.
Jesse
next prev parent reply other threads:[~2004-07-16 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 22:29 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 [this message]
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=200407161042.39748.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=hawkes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome