From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] NR_CPUS: increase maximum NR_CPUS to 4096
Date: Wed, 26 Mar 2008 07:19:25 +0100 [thread overview]
Message-ID: <20080326061925.GC18301@elte.hu> (raw)
In-Reply-To: <20080326014137.934171000@polaris-admin.engr.sgi.com>
* Mike Travis <travis@sgi.com> wrote:
> Increases the limit of NR_CPUS to 4096 and introduces a boolean called
> "MAXSMP" which when set (e.g. "allyesconfig") will set NR_CPUS = 4096
> and NODES_SHIFT = 9 (512).
>
> I've been running this config (4k NR_CPUS, 512 Max Nodes) on an AMD
> box with 2 dual-cores and 4gb memory. I've also successfully booted
> it in a simulated 2cpus/1Gb environment.
cool!
this depends on the cpumask changes to work correctly (i.e. to boot at
all), right?
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] NR_CPUS: increase maximum NR_CPUS to 4096
Date: Wed, 26 Mar 2008 07:19:25 +0100 [thread overview]
Message-ID: <20080326061925.GC18301@elte.hu> (raw)
In-Reply-To: <20080326014137.934171000@polaris-admin.engr.sgi.com>
* Mike Travis <travis@sgi.com> wrote:
> Increases the limit of NR_CPUS to 4096 and introduces a boolean called
> "MAXSMP" which when set (e.g. "allyesconfig") will set NR_CPUS = 4096
> and NODES_SHIFT = 9 (512).
>
> I've been running this config (4k NR_CPUS, 512 Max Nodes) on an AMD
> box with 2 dual-cores and 4gb memory. I've also successfully booted
> it in a simulated 2cpus/1Gb environment.
cool!
this depends on the cpumask changes to work correctly (i.e. to boot at
all), right?
Ingo
--
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:[~2008-03-26 6:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 1:41 [PATCH 0/2] NR_CPUS: increase maximum NR_CPUS to 4096 Mike Travis
2008-03-26 1:41 ` Mike Travis
2008-03-26 1:41 ` [PATCH 1/2] boot: increase stack size for kernel boot loader decompressor Mike Travis
2008-03-26 1:41 ` Mike Travis
2008-03-26 1:41 ` [PATCH 2/2] x86: Modify Kconfig to allow up to 4096 cpus Mike Travis
2008-03-26 1:41 ` Mike Travis
2008-03-26 16:09 ` Adrian Bunk
2008-03-26 16:09 ` Adrian Bunk
2008-03-26 16:31 ` Mike Travis
2008-03-26 16:31 ` Mike Travis
2008-03-26 16:55 ` Adrian Bunk
2008-03-26 16:55 ` Adrian Bunk
2008-03-27 15:06 ` Mike Travis
2008-03-27 15:06 ` Mike Travis
2008-03-26 19:16 ` Christoph Lameter
2008-03-26 19:16 ` Christoph Lameter
2008-03-26 19:28 ` Yinghai Lu
2008-03-26 19:28 ` Yinghai Lu
2008-03-26 6:19 ` Ingo Molnar [this message]
2008-03-26 6:19 ` [PATCH 0/2] NR_CPUS: increase maximum NR_CPUS to 4096 Ingo Molnar
2008-03-26 15:59 ` Mike Travis
2008-03-26 15:59 ` Mike Travis
-- strict thread matches above, loose matches on Subject: below --
2008-04-05 1:30 Mike Travis
2008-04-08 21:53 ` Yinghai Lu
2008-04-08 22:03 ` Mike Travis
2008-04-08 22:32 ` Yinghai Lu
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=20080326061925.GC18301@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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 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.