Re: [PATCH v2 5/5] page_alloc: Bootmem limit with movablecore_map
From: "H. Peter Anvin" <hpa@zytor.com>
Date: 2012-11-26 15:52:14
Also in:
lkml
From: "H. Peter Anvin" <hpa@zytor.com>
Date: 2012-11-26 15:52:14
Also in:
lkml
On 11/26/2012 05:15 AM, Tang Chen wrote:
Hi Wu, That is really a problem. And, before numa memory got initialized, memblock subsystem would be used to allocate memory. I didn't find any approach that could fully address it when I making the patches. There always be risk that memblock allocates memory on ZONE_MOVABLE. I think we can only do our best to prevent it from happening. Your patch is very helpful. And after a shot look at the code, it seems that acpi_numa_memory_affinity_init() is an architecture dependent function. Could we do this somewhere which is not depending on the architecture ?
The movable memory should be classified as a non-RAM type in memblock, that way we will not allocate from it early on. -hpa -- 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>