From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <44F7F376.4030203@kolumbus.fi> Date: Fri, 01 Sep 2006 11:46:46 +0300 From: =?ISO-8859-1?Q?Mika_Penttil=E4?= MIME-Version: 1.0 Subject: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes References: <20060821134518.22179.46355.sendpatchset@skynet.skynet.ie> <20060821134638.22179.44471.sendpatchset@skynet.skynet.ie> <20060831154903.GA7011@skynet.ie> In-Reply-To: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: owner-linux-mm@kvack.org Return-Path: To: Mel Gorman Cc: Keith Mannthey , akpm@osdl.org, tony.luck@intel.com, Linux Memory Management List , ak@suse.de, bob.picco@hp.com, Linux Kernel Mailing List , linuxppc-dev@ozlabs.org List-ID: > > Right, it's all very clear now. At some point in the future, I'd like > to visit why SPARSEMEM-based hot-add is not always used but it's a > separate issue. > >> The add areas >> are marked as RESERVED during boot and then later onlined during add. > > That explains the reserve_bootmem_node() > But pages are marked reserved by default. You still have to alloc the bootmem map for the the whole node range, including reserve hot add areas and areas beyond e820-end-of-ram. So all the areas are already reserved, until freed. --Mika -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org