From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: ak@suse.de, apw@shadowen.org, linux-mm@kvack.org, travis@sgi.com
Subject: Re: [patch 2/2] x86_64: Configure stack size
Date: Fri, 9 Nov 2007 13:10:57 -0800 [thread overview]
Message-ID: <20071109131057.a78c914b.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711091242200.16284@schroedinger.engr.sgi.com>
On Fri, 9 Nov 2007 12:45:06 -0800 (PST)
Christoph Lameter <clameter@sgi.com> wrote:
> On Fri, 9 Nov 2007, Andrew Morton wrote:
>
> > otoh, I doubt if anyone will actually ship an NR_CPUS=16384 kernel, so it
> > isn't terribly pointful.
>
> Our competition (Cray) just announced a product featuring up to 21k
> cpus although that is a cluster. We are definitely getting there...
I'm talking about software, not hardware. I'd expect that you'll have
trouble talking RH/suse/etc into general shipping of an NR_CPUS=16384
kernel.
If I'm correct than I'd have thought that this will be a significant
problem for SGI, so we should find other solutions.
> > So I'm wobbly. Could we please examine the alternatives before proceeding?
>
> This works fine with a 32k stack on IA64 with 4k processors.
yeah, but that's an order-1 allocation on ia64, not an order-3.
> So I tend to
> think of this as a solution that is already working on another platform.
> An 8k stack is also going to be tough with 4k processors on x86_64 which
> we will have soon.
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-11-09 21:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 0:43 [patch 0/2] X86_64 configurable " clameter
2007-11-07 0:43 ` [patch 1/2] x86_64: Clean up stack allocation and free clameter
2007-11-07 19:11 ` Andy Whitcroft
2007-11-07 0:43 ` [patch 2/2] x86_64: Configure stack size clameter
2007-11-07 19:14 ` Andy Whitcroft
2007-11-07 23:12 ` Andi Kleen
2007-11-08 0:42 ` Christoph Lameter
2007-11-09 20:13 ` Andrew Morton
2007-11-09 20:45 ` Christoph Lameter
2007-11-09 21:10 ` Andrew Morton [this message]
2007-11-09 21:19 ` Christoph Lameter
2007-11-09 21:46 ` Andrew Morton
2007-11-09 21:50 ` Christoph Lameter
2007-11-10 17:21 ` Andi Kleen
[not found] <Pine.LNX.4.64.0711121147350.27017@schroedinger.engr.sgi.com>
2007-11-19 18:19 ` Mike Travis
2007-11-19 20:05 ` Andi Kleen
2007-11-19 22:35 ` 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=20071109131057.a78c914b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=travis@sgi.com \
/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