From: Erich Focht <efocht@hpce.nec.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Hugh Dickins <hugh@veritas.com>,
linux-mm@kvack.org, linux-ia64@vger.kernel.org
Subject: Re: removing mm->rss and mm->anon_rss from kernel?
Date: Mon, 08 Nov 2004 16:30:37 +0000 [thread overview]
Message-ID: <200411081730.37906.efocht@hpce.nec.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0411080800020.7996@schroedinger.engr.sgi.com>
On Monday 08 November 2004 17:04, Christoph Lameter wrote:
> Nope. The future of computing seems to be very high numbers of cpus.
> NASAs Columbia has 10k cpus and the new BlueGen solution from IBM is
> already at 8k.
You're talking about clusters, i.e. multiple running instances of the
operating system. I don't think anybody really wants to go far beyond
512 nowadays. Application-wise 512 cpus/node isn't really needed (but
sometimes nice to have, for marketting). Beyond problems with
scalability of the interconnect (and very uneven latency distribution)
bigger systems would accumulate a too small MTBF. When a broken CPU,
DIMM or other chip takes your entire >1k CPU-machine down, you'll
hapilly exchage it agains a cluster.
Erich
next prev parent reply other threads:[~2004-11-08 16:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4189EC67.40601@yahoo.com.au>
[not found] ` <Pine.LNX.4.58.0411040820250.8211@schroedinger.engr.sgi.com>
[not found] ` <418AD329.3000609@yahoo.com.au>
[not found] ` <Pine.LNX.4.58.0411041733270.11583@schroedinger.engr.sgi.com>
[not found] ` <418AE0F0.5050908@yahoo.com.au>
[not found] ` <418AE9BB.1000602@yahoo.com.au>
[not found] ` <1099622957.29587.101.camel@gaston>
[not found] ` <418C55A7.9030100@yahoo.com.au>
2004-11-06 9:28 ` removing mm->rss and mm->anon_rss from kernel? Christoph Lameter
[not found] ` <204290000.1099754257@[10.10.2.4]>
2004-11-06 16:19 ` Christoph Lameter
2004-11-06 20:05 ` William Lee Irwin III
2004-11-07 16:11 ` Martin J. Bligh
2004-11-07 18:25 ` Matthew Wilcox
2004-11-08 12:43 ` Jesse Barnes
2004-11-08 15:26 ` Andi Kleen
2004-11-08 16:07 ` Christoph Lameter
2004-11-08 16:04 ` Christoph Lameter
2004-11-08 16:12 ` Anton Blanchard
2004-11-08 16:14 ` Martin J. Bligh
2004-11-08 16:25 ` Christoph Lameter
2004-11-08 16:30 ` Erich Focht [this message]
2004-11-08 16:57 ` Diego Calleja
2004-11-08 17:26 ` Erich Focht
2004-11-10 11:57 ` Magnus Damm
2004-11-06 20:51 ` Rik van Riel
2004-11-08 15:47 ` Russ Anderson
2004-11-08 16:08 ` Martin J. Bligh
2004-11-10 4:52 ` Nick Piggin
2004-11-10 17:30 ` Robin Holt
2004-11-10 18:50 ` Ray Bryant
2004-11-12 23:45 ` Ray Bryant
2004-11-13 0:05 ` Steve Neuner
2004-11-08 16:35 ` Rik van Riel
2004-11-08 16:56 ` Hugh Dickins
2004-11-08 17:01 ` Christoph Lameter
2004-11-09 2:40 ` Nick Piggin
2004-11-09 12:10 ` Matthew Wilcox
2004-11-10 0:48 ` Nick Piggin
2004-11-12 0:38 ` Christoph Lameter
2004-11-12 12:50 ` Robin Holt
2004-11-12 15:02 ` Christoph Lameter
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=200411081730.37906.efocht@hpce.nec.com \
--to=efocht@hpce.nec.com \
--cc=benh@kernel.crashing.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.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