linux-kernel - Why are the pages not migrated to current cpuset after 'memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Dec 2008 13:11:57 +0800
From:	Miao Xie <miaox@...fujitsu.com>
To:	Paul Menage <menage@...gle.com>
CC:	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Why are the pages not migrated to current cpuset after 'memory_migrate'
 is set true

Hi, Paul

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) 
 
Regards
Miao Xie

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/