Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756054Ab0KUVqQ (ORCPT ); Sun, 21 Nov 2010 16:46:16 -0500 Received: from smtp-out.google.com ([216.239.44.51]:52355 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755838Ab0KUVqO (ORCPT ); Sun, 21 Nov 2010 16:46:14 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version:content-type; b=uCST6rHFnptymnBU1wTJYauPK4mCOEWppxGO2BOlZjhp4Iu1eAwxv+G3xOQdvvKpj2 F6nTZoOw/bqtqkdF0ANQ== Date: Sun, 21 Nov 2010 13:46:07 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: =?UTF-8?Q?Am=C3=A9rico_Wang?= 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 In-Reply-To: <20101121142615.GI9099@hack> Message-ID: References: <20101117075128.GA30254@shaohui> <20101118041407.GA2408@shaohui> <20101118062715.GD17539@linux-sh.org> <20101118052750.GD2408@shaohui> <20101119003225.GB3327@shaohui> <20101121142615.GI9099@hack> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="531368966-2030196969-1290375970=:26304" X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1360 Lines: 34 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --531368966-2030196969-1290375970=:26304 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Sun, 21 Nov 2010, Américo Wang wrote: > 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? > This is outside the scope of node hotplug emulation, it needs to be built on top of whatever the kernel implements. > 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. --531368966-2030196969-1290375970=:26304-- -- 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/