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.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()
--Mika - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 0/6] Sizing zones and holes in an architecture independent manner V9
- From: Mel Gorman <[email protected]>
- [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- From: Mel Gorman <[email protected]>
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- From: "Keith Mannthey" <[email protected]>
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- From: [email protected] (Mel Gorman)
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- From: "Keith Mannthey" <[email protected]>
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- From: Mel Gorman <[email protected]>
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- From: "Keith Mannthey" <[email protected]>
- Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- From: Mel Gorman <[email protected]>
- [PATCH 0/6] Sizing zones and holes in an architecture independent manner V9
- Prev by Date: Re: x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.
- Next by Date: Re: Patch to make VIA sata board bootable again.
- Previous by thread: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- Next by thread: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- Index(es):
 |