[lkml]   [2010]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 1/7] Allow CONFIG_MIGRATION to be set without CONFIG_NUMA

    On Thu, 7 Jan 2010, David Rientjes wrote:

    > CONFIG_MIGRATION is no longer strictly dependent on CONFIG_NUMA since
    > ARCH_ENABLE_MEMORY_HOTREMOVE has allowed it to be configured for UMA
    > machines. All strictly NUMA features in the migration core should be
    > isolated under its #ifdef CONFIG_NUMA (sys_move_pages()) in mm/migrate.c
    > or by simply not compiling mm/mempolicy.c (sys_migrate_pages()), so this
    > patch looks fine as is (although the "help" text for CONFIG_MIGRATION
    > could be updated to reflect that it's useful for both memory hot-remove
    > and now compaction).


    Reviewed-by: Christoph Lameter <>

     \ /
      Last update: 2010-01-07 23:07    [W:0.020 / U:15.964 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site