From: "John Hawkes" <hawkes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Setup an IA64 specific reclaim distance
Date: Fri, 14 Apr 2006 17:36:40 +0000 [thread overview]
Message-ID: <002101c65fe9$fd76fc50$6f00a8c0@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604131823410.16211@schroedinger.engr.sgi.com>
From: "Christoph Lameter" <clameter@sgi.com>
> > Is the right value for this any any way related to the "migration_cost"
> > that we spend many seconds of boot time computing?
>
> I am not familiar with that. Does the migration_cost take the
> SLIT node distances into consideration?
No. The migration_cost is an empirical runtime calculation that estimates the
relative cost of migrating a task within each level of sched domain. And even
that is sometimes grossly inaccurate because only two arbitrary CPUs are
chosen for this calculation within one sched domain at each level, thus
assuming that the migration_cost is the same between any and all two CPUs in
that sched domain, and that all the sched domains for a given level exhibit
equivalent migration_cost behavior.
For example, one level of sched domain is the all-CPUs sched domain. For a
NUMA system it is unlikely that the migration_cost between cpu0 and cpu1 is
the same as between cpu0 and cpu511, and yet only cpu0 and cpu1 are chosen.
Another sched domain level on sn2 platforms, typically two CPUs per node, is
32p. Again, there the migration_cost between cpu0 and cpu1 is different than
cpu0 and cpu31.
John Hawkes
next prev parent reply other threads:[~2006-04-14 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 1:23 Setup an IA64 specific reclaim distance Christoph Lameter
2006-04-14 16:18 ` Luck, Tony
2006-04-14 16:44 ` Christoph Lameter
2006-04-14 17:36 ` John Hawkes [this message]
2006-04-14 17:39 ` Luck, Tony
2006-04-14 17:41 ` Christoph Lameter
2006-04-14 17:43 ` Luck, Tony
2006-04-14 17:43 ` Christoph Lameter
2006-04-14 17:44 ` Luck, Tony
2006-04-14 17:54 ` Luck, Tony
2006-04-14 18:04 ` John Hawkes
2006-04-14 18:06 ` Christoph Lameter
2006-04-14 18:08 ` Christoph Lameter
2006-04-14 18:22 ` Chen, Kenneth W
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='002101c65fe9$fd76fc50$6f00a8c0@comcast.net' \
--to=hawkes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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