Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753685Ab0KUOXL (ORCPT ); Sun, 21 Nov 2010 09:23:11 -0500 Received: from mail-pv0-f174.google.com ([74.125.83.174]:55495 "EHLO mail-pv0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753421Ab0KUOXJ (ORCPT ); Sun, 21 Nov 2010 09:23:09 -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:in-reply-to:user-agent; b=RUmh7yNC2qWzi/7yPqC0Sh1xTbqEHOH89am8cJFpwNtjKGA8ED5b2+xGZw03p4hcxC gtdl1MIsL/vsN9tyT6/hJjW56Vdd4PCKN0x9Xk/JwPIMqwldgtyhIXqBxd/NLXVmEWL4 2WohPEKvYxaZH09TWxvRZ2xeIa44Y3w6AbVVU= Date: Sun, 21 Nov 2010 22:26:15 +0800 From: =?utf-8?Q?Am=C3=A9rico?= Wang To: David Rientjes Cc: 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: <20101121142615.GI9099@hack> References: <20101117075128.GA30254@shaohui> <20101118041407.GA2408@shaohui> <20101118062715.GD17539@linux-sh.org> <20101118052750.GD2408@shaohui> <20101119003225.GB3327@shaohui> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: 1065 Lines: 30 Hi, David On Sat, Nov 20, 2010 at 06:28:31PM -0800, David Rientjes wrote: >Adds a numa=possible= command line option to set an additional N nodes >as being possible for memory hotplug. This set of possible nodes >controls nr_node_ids and the sizes of several dynamically allocated node >arrays. > >This allows memory hotplug to create new nodes for newly added memory >rather than binding it to existing nodes. > >The first use-case for this will be node hotplug emulation which will use >these possible nodes to create new nodes to test the memory hotplug >callbacks and surrounding memory hotplug code. > I am not sure how much value of making this dynamic, for CPU, we do this at compile time, i.e. NR_CPUS, so how about NR_NODES? Also, numa=possible= is not as clear as numa=max=, for me at least. 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/