[lkml]   [2012]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 5/5] page_alloc: Bootmem limit with movablecore_map
On 2012/11/26 23:48, H. Peter Anvin wrote:

> 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

yep, we can put movable memory in reserved.regions in memblock.

> .

 \ /
  Last update: 2012-11-27 02:41    [W:1.125 / U:2.928 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site