From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
"Martin J. Bligh" <mbligh@aracnet.com>,
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 11:30:44 -0400 [thread overview]
Message-ID: <200407161130.44616.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040716150418.GA5195@taniwha.stupidest.org>
On Friday, July 16, 2004 11:04 am, Chris Wedgwood wrote:
> On Fri, Jul 16, 2004 at 10:45:38AM -0400, Jesse Barnes wrote:
> > For sn2 at least, there are quite a few ways we could dice up the
> > topology. We'll have to experiment with things a bit to find some
> > good defaults.
>
> The PROM can export topology details so presumably there is enough to
> derive something sane on boot surely?
Yep, we should have all the information we need, it's just a matter of
translating it into something useful. Since routers tend to group together
nodes in groups of 4 or 8, a node herd with that many nodes might make sense,
but also might be too small. We might want everything within a set of
metarouters in a group instead, or in addition, or...
Jesse
next prev parent reply other threads:[~2004-07-16 15:31 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 [this message]
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=200407161130.44616.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=cw@f00f.org \
--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