From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
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:19:11 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711091313040.16547@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20071109131057.a78c914b.akpm@linux-foundation.org>
On Fri, 9 Nov 2007, Andrew Morton wrote:
> 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.
Yeah that is one reason why I removed all percpu arrays from the kernel
with the cpu_alloc patchset. I think we can get to a point where this does
not hurt that much. We want to be as close as possible to a distro kernel
as possible.
> > If I'm correct than I'd have thought that this will be a significant
> problem for SGI, so we should find other solutions.
Maybe a special kernel from the distros is unavoidable but then they have
done that in the past for us too. Certainly we do not want to have the
kernel patches just for HPC apps. This is an option after all and not a
default. Mike Travis is working on reducing the per cpu overhead in the
x86_64 arch code. So we should be getting to a pretty good situation even
if we have to leave the cpumasks alone.
> > > 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.
Well the default is also an order-1 allocation on x86_64. The order-3
alloc is not going to be that much of a problem if you have a system with
several terabytes of RAM.
--
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:19 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
2007-11-09 21:19 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0711091313040.16547@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--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