[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47EA72E9.4060307@sgi.com>
Date: Wed, 26 Mar 2008 08:59:37 -0700
From: Mike Travis <travis@....com>
To: Ingo Molnar <mingo@...e.hu>
CC: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] NR_CPUS: increase maximum NR_CPUS to 4096
Ingo Molnar wrote:
> * Mike Travis <travis@....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
Yes, it overflows the stack quite quickly without the cpumask changes.
I didn't do any testing to see what's the minimal set of changes.
Thanks,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists