From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Jesse Barnes <jbarnes@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: Whining about NUMA. :) [Was whining about 2.5...]
Date: Mon, 08 Oct 2001 12:20:59 -0700 [thread overview]
Message-ID: <1816279834.1002543659@mbligh.des.sequent.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0110081548020.4899-100000@freak.distro.conectiva>
>> That's what I was planning on ... we'd need m x n classzones, where m
>> was the number of levels, and n the number of nodes. Each search would
>> obviously be through m classzones. I'll go poke at the current code some more.
>
> You say "numbers of levels" as in each level being a given number of nodes
> on that "level" distance ?
Yes.
For example, if the only different access speeds you have were "on the local
node" vs "on another node", and access times to all *other* nodes were the
same, you'd have 2 levels.
If you have "on the local node" (10 ns) vs "on any node 1 hop away" (100ns),
"on any node 2 hops away" (110ns), that'd be 3 levels. (latency numbers picked
out of my portable random number generator ;-) ).
If the latencies on a 4 level system turn out to be 10,100,101,102 then it's only
going to be worth defining 2 levels. If they turn out to be 10,100,1000, 10000,
then it'll (probably) be worth doing 4 ....
M.
next prev parent reply other threads:[~2001-10-08 19:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 12:17 bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2 Vladimir V. Saveliev
2001-10-03 13:16 ` [PATCH] " Alexander Viro
2001-10-03 16:18 ` Linus Torvalds
2001-10-03 21:43 ` Alexander Viro
2001-10-03 21:56 ` Christoph Hellwig
2001-10-03 22:51 ` Alexander Viro
2001-10-03 19:55 ` Whining about 2.5 (was Re: [PATCH] Re: bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2) Rob Landley
2001-10-04 0:38 ` Rik van Riel
2001-10-03 22:27 ` Rob Landley
2001-10-04 20:53 ` Whining about 2.5 (was Re: [PATCH] Re: bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2O Alan Cox
2001-10-04 23:59 ` Whining about NUMA. :) [Was whining about 2.5...] Rob Landley
2001-10-05 14:51 ` Alan Cox
2001-10-08 17:57 ` Martin J. Bligh
2001-10-08 18:10 ` Alan Cox
2001-10-08 18:20 ` Martin J. Bligh
2001-10-08 18:31 ` Alan Cox
2001-10-08 18:35 ` Jesse Barnes
2001-10-08 18:55 ` Martin J. Bligh
2001-10-08 17:48 ` Marcelo Tosatti
2001-10-08 19:20 ` Martin J. Bligh [this message]
2001-10-08 19:12 ` Jesse Barnes
2001-10-08 19:37 ` Peter Rival
2001-10-04 23:39 ` NUMA & classzones (was Whining about 2.5) Martin J. Bligh
2001-10-04 23:55 ` Rob Landley
2001-10-05 17:29 ` Martin J. Bligh
2001-10-06 1:44 ` Jesse Barnes
2001-10-04 21:02 ` Whining about 2.5 (was Re: [PATCH] Re: bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2) Alan Cox
2001-10-03 21:09 ` Buffer cache confusion? Re: [reiserfs-list] bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2 Eric Whiting
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=1816279834.1002543659@mbligh.des.sequent.com \
--to=martin.bligh@us.ibm.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®