lkml.org 
[lkml]   [2008]   [Dec]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: Why are the pages not migrated to current cpuset after 'memory_migrate' is set true
    From
    On Mon, Dec 15, 2008 at 9:11 PM, Miao Xie <miaox@cn.fujitsu.com> wrote:
    > I found the pages that task had allocated to it on nodes in its previous cpuset
    > were not migrated to the tasks' current cpuset after 'memory_migrate' was set
    > true. It looks strange for users. Why are the pages not migrated to current
    > cpuset after 'memory_migrate' is set true?
    >
    > Step I did
    > 1, allocate pages on cpuset (mems is 0, memory_migrate is 0)
    > 2, change cpuset's mems (mems: 0 -> 1)
    > 3, change cpuset's memory_migrate(memory_migrate: 0 -> 1)

    As Daisuke says, migration only occurs when the mems file is changed
    *after* memory_migrate has been set to 1.

    Paul


    \
     
     \ /
      Last update: 2008-12-16 09:27    [W:0.019 / U:118.748 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site