Re: [PATCH v7 4/8] mm,memory_hotplug: Allocate memmap from the added memory range

2021-04-16 Thread David Hildenbrand
On 16.04.21 09:25, Oscar Salvador wrote: On Thu, Apr 15, 2021 at 01:19:59PM +0200, David Hildenbrand wrote: Implementation wise we will reuse vmem_altmap infrastructure to override the default allocator used by __populate_section_memmap. Part of the implementation also relies on memory_block str

Re: [PATCH v7 4/8] mm,memory_hotplug: Allocate memmap from the added memory range

2021-04-16 Thread Oscar Salvador
On Thu, Apr 15, 2021 at 01:19:59PM +0200, David Hildenbrand wrote: > > Implementation wise we will reuse vmem_altmap infrastructure to override > > the default allocator used by __populate_section_memmap. > > Part of the implementation also relies on memory_block structure gaining > > a new field w

Re: [PATCH v7 4/8] mm,memory_hotplug: Allocate memmap from the added memory range

2021-04-15 Thread David Hildenbrand
On 08.04.21 14:18, Oscar Salvador wrote: Physical memory hotadd has to allocate a memmap (struct page array) for the newly added memory section. Currently, alloc_pages_node() is used for those allocations. This has some disadvantages: a) an existing memory is consumed for that purpose (eg

[PATCH v7 4/8] mm,memory_hotplug: Allocate memmap from the added memory range

2021-04-08 Thread Oscar Salvador
Physical memory hotadd has to allocate a memmap (struct page array) for the newly added memory section. Currently, alloc_pages_node() is used for those allocations. This has some disadvantages: a) an existing memory is consumed for that purpose (eg: ~2MB per 128MB memory section on x86_64) b