All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rival <frival@zk3.dec.com>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Whining about NUMA. :)  [Was whining about 2.5...]
Date: Mon, 08 Oct 2001 15:37:27 -0400	[thread overview]
Message-ID: <3BC20077.6020706@zk3.dec.com> (raw)
In-Reply-To: <Pine.SGI.4.21.0110081207520.1003634-100000@spamtin.engr.sgi.com>

Just to put in my $0.02 on this...  Compaq systems will span the range 
on this.  The current Wildfire^WGS Series systems have two levels - 
either "local" or "remote", which is just under 3:1 latency vs. local. 
This is all public knowledge, if you care to dig through all the docs. ;)

With the new EV7 systems coming out soon (next year?) every CPU has a 
switch and memory controller built in, so as you add CPUs (up to 64) you 
potentially add levels of latency.  I can't say what they are, but the 
numbers I've been given so far are _much_ better than that.  Just 
another data point. :)

  - Pete


  reply	other threads:[~2001-10-08 19:39 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
2001-10-08 19:12                                 ` Jesse Barnes
2001-10-08 19:37                                   ` Peter Rival [this message]
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=3BC20077.6020706@zk3.dec.com \
    --to=frival@zk3.dec.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=jbarnes@sgi.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.