Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755487AbZGARW7 (ORCPT ); Wed, 1 Jul 2009 13:22:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753804AbZGARWj (ORCPT ); Wed, 1 Jul 2009 13:22:39 -0400 Received: from smtp3.ultrahosting.com ([74.213.175.254]:54768 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754451AbZGARWh (ORCPT ); Wed, 1 Jul 2009 13:22:37 -0400 Date: Wed, 1 Jul 2009 13:22:33 -0400 (EDT) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: yakui cc: "Li, Shaohua" , "akpm@linux-foundation.org" , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , "mel@csn.ul.ie" Subject: Re: + memory-hotplug-alloc-page-from-other-node-in-memory-online.patch added to -mm tree In-Reply-To: <1246419543.18688.14.camel@localhost.localdomain> Message-ID: References: <200906291949.n5TJnuov028806@imap1.linux-foundation.org> <20090630004735.GA21254@sli10-desk.sh.intel.com> <20090701025558.GA28524@sli10-desk.sh.intel.com> <1246419543.18688.14.camel@localhost.localdomain> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1171 Lines: 26 On Wed, 1 Jul 2009, yakui wrote: > If we can't allocate memory from other node when there is no memory on > this node, we will have to do something like the bootmem allocator. > After the memory page is added to the system memory, we will have to > free the memory space used by the memory allocator. At the same time we > will have to assure that the hot-plugged memory exists physically. The bootmem allocator must stick around it seems. Its more like a node bootstrap allocator then. Maybe we can generalize that. The bootstrap allocator may only need to be able boot one node (which simplifies design). During system bringup only the boot node is brought up. Then the other nodes are hotplugged later all in turn using the bootstrap allocator for their node setup? There are a couple of things where one would want to spread out memory across the nodes at boot time. How would node hotplugging handle that situation? -- 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/