lkml.org 
[lkml]   [2012]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v2 5/5] page_alloc: Bootmem limit with movablecore_map
    At 11/26/2012 11:48 PM, 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.

    Hi, hpa

    The problem is that:
    node1 address rang: [18G, 34G), and the user specifies movable map is [8G, 24G).
    We don't know node1's address range before numa init. So we can't prevent
    allocating boot memory in the range [24G, 34G).

    The movable memory should be classified as a non-RAM type in memblock. What
    do you want to say? We don't save type in memblock because we only
    add E820_RAM and E820_RESERVED_KERN to memblock.

    Thanks
    Wen Congyang

    >
    > -hpa
    >
    >



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