public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
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 00:23:30 +0000	[thread overview]
Message-ID: <20051110002330.GA9219@sgi.com> (raw)
In-Reply-To: <20051027041709.GA13193@attica.americas.sgi.com>

On Thu, Nov 10, 2005 at 01:03:44AM +0100, Gerald Pfeifer wrote:
> On Wed, 9 Nov 2005, Luck, Tony wrote:
> > But don't you already have that issue with persuading them to ship with 
> > CONFIG_NR_CPUS\x16384?  Surely there are a whole boatload of tuneables 
> > and patches needed to get this sized system up and running? 4-level 
> > pagetables are just one piece of the puzzle.
> 
> 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. ;-)
> 
> Gerald

True, nothing this big is proposed for inclusion in SLES. The current max
for NR_CPUS is 1024. 

MAX_NUMALINK_NODES is the number of nodes in all SSI clusters that are 
connected by NUMALINK. Single kernels are still restricted to 256 
nodes & 1024 cpus.


-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.



  parent reply	other threads:[~2005-11-10  0:23 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 [this message]
2005-11-10  0:27 ` Luck, Tony
2005-11-10  2:54 ` Jack Steiner
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=20051110002330.GA9219@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