Re: [RFC 4/4] Sparse initialization of struct page array.

From: Yinghai Lu
Date: Thu Jul 25 2013 - 08:51:03 EST

On Wed, Jul 24, 2013 at 7:25 PM, Robin Holt <holt@xxxxxxx> wrote:
>> How about holes that is not in memblock.reserved?
>> before this patch:
>> free_area_init_node/free_area_init_core/memmap_init_zone
>> will mark all page in node range to Reserved in struct page, at first.
>> but those holes is not mapped via kernel low mapping.
>> so it should be ok not touch "struct page" for them.
>> Now you only mark reserved for memblock.reserved at first, and later
>> mark {memblock.memory} - { memblock.reserved} to be available.
>> And that is ok.
>> but should split that change to another patch and add some comment
>> and change log for the change.
>> in case there is some user like UEFI etc do weird thing.
> Nate and I talked this over today. Sorry for the delay, but it was the
> first time we were both free. Neither of us quite understands what you
> are asking for here. My interpretation is that you would like us to
> change the use of the PageReserved flag such that during boot, we do not
> set the flag at all from memmap_init_zone, and then only set it on pages
> which, at the time of free_all_bootmem, have been allocated/reserved in
> the memblock allocator. Is that correct? I will start to work that up
> on the assumption that is what you are asking for.

Not exactly.

your change should be right, but there is some subtle change about
holes handling.

before mem holes between memory ranges in memblock.memory, get struct page,
and initialized with to Reserved in memmap_init_zone.
Those holes is not in memory.reserved, with your patches, those hole's
struct page
will still have all 0.

Please separate change about set page to reserved according to memory.reserved
to another patch.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at