From: Christoph Lameter <clameter@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Andy Whitcroft <apw@shadowen.org>,
akpm@linux-foundation.org, linux-mm@kvack.org, travis@sgi.com
Subject: Re: [patch 2/2] x86_64: Configure stack size
Date: Wed, 7 Nov 2007 16:42:04 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711071639491.4640@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200711080012.06752.ak@suse.de>
On Thu, 8 Nov 2007, Andi Kleen wrote:
>
> > We seem to be growing two different mechanisms here for 32bit and 64bit.
> > This does seem a better option than that in 32bit CONFIG_4KSTACKS etc.
> > IMO when these two merge we should consolidate on this version.
>
> Best would be to not change it at all for 64bit for now.
>
> We can worry about the 16k CPU systems when they appear, but shorter term
> it would just lead to other crappy kernel code relying on large stacks when
> it shouldn't.
Well we cannot really test these systems without these patches and when
they become officially available then its too late for merging.
--
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-08 0:42 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 [this message]
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
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.0711071639491.4640@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