lkml.org 
[lkml]   [2013]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v5 0/5] Add movablecore_map boot option
    On 01/16/2013 01:29 PM, Andrew Morton wrote:
    >>
    >> Yes. If SRAT support is available, all memory which enabled hotpluggable
    >> bit are managed by ZONEMOVABLE. But performance degradation may
    >> occur by NUMA because we can only allocate anonymous page and page-cache
    >> from these memory.
    >>
    >> In this case, if user cannot change SRAT information, user needs a way to
    >> select/set removable memory manually.
    >
    > If I understand this correctly you mean that once SRAT parsing is
    > implemented, the user can use movablecore_map to override that SRAT
    > parsing, yes? That movablecore_map will take precedence over SRAT?
    >

    Yes, but we still need a higher-level user interface which specifies
    which nodes, not which memory ranges, should be movable. That is the
    policy granularity that is actually appropriate for the administrator
    (trading off performance vs reliability.)

    -hpa



    \
     
     \ /
      Last update: 2013-01-17 00:21    [W:4.831 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site