From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <clameter@sgi.com>,
ak@suse.de, apw@shadowen.org, linux-mm@kvack.org, travis@sgi.com
Subject: Re: [patch 2/2] x86_64: Configure stack size
Date: Sat, 10 Nov 2007 18:21:47 +0100 [thread overview]
Message-ID: <20071110172146.GF22277@bingen.suse.de> (raw)
In-Reply-To: <20071109121332.7dd34777.akpm@linux-foundation.org>
> What else can we do? Change all sites to do some dynamic allocation if
> (NR_CPUS >= lots), I guess.
I think that's an reasonable alternative. Perhaps push one or two into
task_struct and grab them from there, then go dynamic. Only issue
is error handling and making it look nice in the source.
> As for timing: we might as well merge it now so that 2.6.25 has at least a
> chance of running on 16384-way.
x86 is still limited to 256 virtual CPUs. What makes you think that changed?
With x2APIC from Intel it will be higher, but I haven't seen code for
that yet.
> otoh, I doubt if anyone will actually ship an NR_CPUS=16384 kernel, so it
> isn't terribly pointful.
NR_CPUS==4096 might happen. Of course that still needs eliminating
a lot of NR_CPUS arrays and fixing up of NR_INTERRUPTS and some other
things.
-Andi
--
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-10 17:21 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 stack size 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
2007-11-09 21:46 ` Andrew Morton
2007-11-09 21:50 ` Christoph Lameter
2007-11-10 17:21 ` Andi Kleen [this message]
[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=20071110172146.GF22277@bingen.suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.