Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752610Ab0KVPkL (ORCPT ); Mon, 22 Nov 2010 10:40:11 -0500 Received: from mail-gy0-f174.google.com ([209.85.160.174]:48556 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750926Ab0KVPkI (ORCPT ); Mon, 22 Nov 2010 10:40:08 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; b=OYV4kVMAl7cc4SEiMvbFPhP4rgbg6R0XcU6DFD1XKpuLbbs405RqYxuwpXPwRIb8wr dc5Xvwn7JMKl/oXjllJ9kOOqwQh3f42ZHg0LkNUXbQ+Ik4pmJNAxDn6RPjnyt3LaXJMB hYBy5mV2P4mZpBOoWvm/i4YVOejBm0cjXyY24= Date: Mon, 22 Nov 2010 23:43:17 +0800 From: =?utf-8?Q?Am=C3=A9rico?= Wang To: David Rientjes Cc: =?utf-8?Q?Am=C3=A9rico?= Wang , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner , Greg Kroah-Hartman , Shaohui Zheng , Paul Mundt , Andrew Morton , Andi Kleen , Yinghai Lu , Haicheng Li , Randy Dunlap , linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org Subject: Re: [patch 1/2] x86: add numa=possible command line option Message-ID: <20101122154317.GC4137@hack> References: <20101118041407.GA2408@shaohui> <20101118062715.GD17539@linux-sh.org> <20101118052750.GD2408@shaohui> <20101119003225.GB3327@shaohui> <20101121142615.GI9099@hack> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 984 Lines: 24 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/