From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] 4-level page table directories.
Date: Thu, 10 Nov 2005 02:54:21 +0000 [thread overview]
Message-ID: <20051110025421.GA3765@sgi.com> (raw)
In-Reply-To: <20051027041709.GA13193@attica.americas.sgi.com>
On Wed, Nov 09, 2005 at 04:27:48PM -0800, Luck, Tony wrote:
> >Is it possible you are mixing up MAX_NUMALINK_NODES (the maximum
> >system size, i.e., the maximum number of nodes in a numalink domain)
> >with CONFIG_NR_CPUS (the maximum SSI size)?
> >
> >I'm pretty confident SGI has not proposed setting CONFIG_NR_CPUS\x16384
> >to any OSV. ;-)
>
> It's always possible that I'm confused. Here's the message where
> Robin introduced the rationale for 4-level page tables:
You are not confused, but this is a confusing area. A lot of
the terminology that we use to describe these configurations has
been misused or poorly defined.
Altix currently supports a max SSI of 256 nodes (1024p). However, multiple
SSIs can be interconnected via NUMALINK.
XPMEM provides the ability for a single task running within an SSI
to access ALL the memory thruout the NUMALINK fabric, ie. memory
can be exported from a task running within one SSI to a task
running in another SSI.
For example, if you have:
128 GB per SSI
16 SSIs connected via NUMALINK
a task running within an SSI can access all 2TB of memory (excluding memory
used by the kernel)
Note: SSI = fat node = cluster
>
> http://tinyurl.com/bewsk
>
> In that he says "current = 2048" ... which I think is how many
> cpus can be in the whole box ... 512 is the current max cpus in
> a coherence domain (and thus the max that a single instance of
> Linux will see today).
>
> With Montecito (dual core, two threads in each core) the number
> of cpus Linux sees will be quadrupled in a system with the same
> number of sockets. Add more sockets, and the 16384 number may
> not be impossible.
>
> -Tony
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next prev parent reply other threads:[~2005-11-10 2:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 4:17 [RFC] 4-level page table directories Robin Holt
2005-10-28 5:19 ` Ian Wienand
2005-10-28 11:19 ` Robin Holt
2005-10-28 23:23 ` Luck, Tony
2005-10-28 23:55 ` Chen, Kenneth W
2005-10-29 0:49 ` Grant Grundler
2005-10-29 2:18 ` David Mosberger-Tang
2005-11-01 12:13 ` Robin Holt
2005-11-01 15:41 ` David Mosberger-Tang
2005-11-02 10:35 ` Robin Holt
2005-11-02 13:26 ` Robin Holt
2005-11-02 16:11 ` Luck, Tony
2005-11-02 16:23 ` Robin Holt
2005-11-02 16:30 ` Luck, Tony
2005-11-02 17:16 ` Robin Holt
2005-11-02 18:59 ` David Mosberger-Tang
2005-11-02 22:26 ` Ian Wienand
2005-11-03 1:36 ` Gerald Pfeifer
2005-11-03 1:53 ` Chen, Kenneth W
2005-11-03 3:55 ` Jack Steiner
2005-11-03 16:36 ` Robin Holt
2005-11-03 19:59 ` Chen, Kenneth W
2005-11-04 17:58 ` Luck, Tony
2005-11-04 21:37 ` Robin Holt
2005-11-04 21:42 ` Chen, Kenneth W
2005-11-04 22:50 ` Chen, Kenneth W
2005-11-07 21:18 ` Luck, Tony
2005-11-08 0:22 ` Rohit Seth
2005-11-08 12:43 ` Robin Holt
2005-11-08 18:23 ` Boehm, Hans
2005-11-08 18:52 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-08 18:56 ` Rohit Seth
2005-11-08 19:36 ` Robin Holt
2005-11-08 20:07 ` Chen, Kenneth W
2005-11-08 20:27 ` Chen, Kenneth W
2005-11-08 22:09 ` Ian Wienand
2005-11-08 23:58 ` Gerald Pfeifer
2005-11-09 0:08 ` David Mosberger-Tang
2005-11-09 0:22 ` Rohit Seth
2005-11-09 0:46 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-09 1:18 ` Chen, Kenneth W
2005-11-09 12:11 ` Robin Holt
2005-11-09 14:29 ` Robin Holt
2005-11-09 18:22 ` Chen, Kenneth W
2005-11-09 18:39 ` Luck, Tony
2005-11-10 0:03 ` Gerald Pfeifer
2005-11-10 0:23 ` Jack Steiner
2005-11-10 0:27 ` Luck, Tony
2005-11-10 2:54 ` Jack Steiner [this message]
2005-11-10 9:13 ` Robin Holt
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=20051110025421.GA3765@sgi.com \
--to=steiner@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