[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101122154317.GC4137@hack>
Date: Mon, 22 Nov 2010 23:43:17 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: David Rientjes <rientjes@...gle.com>
Cc: Américo Wang <xiyou.wangcong@...il.com>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Greg Kroah-Hartman <gregkh@...e.de>,
Shaohui Zheng <shaohui.zheng@...el.com>,
Paul Mundt <lethal@...ux-sh.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <ak@...ux.intel.com>,
Yinghai Lu <yinghai@...nel.org>,
Haicheng Li <haicheng.li@...el.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, x86@...nel.org
Subject: Re: [patch 1/2] x86: add numa=possible command line option
On Sun, Nov 21, 2010 at 01:46:07PM -0800, David Rientjes wrote:
>On Sun, 21 Nov 2010, Américo Wang wrote:
>> Also, numa=possible= is not as clear as numa=max=, for me at least.
>>
>
>I like name, but it requires that you know how many nodes that system
>already has. In other words, numa=possible=4 allows you to specify that 4
>additional nodes will be possible, but initially offline, for this or
>other purposes. numa=max=4 would be no-op if the system actually had 4
>nodes.
>
>I chose numa=possible over numa=additional because it is more clearly tied
>to node_possible_map, which is the only thing it modifies.
Okay, I thought "possible" means "max", but "possible" means "addtional" here.
It's clear for me now.
Thanks!
--
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