From: Miao Xie <miaox@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Why are the pages not migrated to current cpuset after 'memory_migrate' is set true
Date: Tue, 16 Dec 2008 13:11:57 +0800 [thread overview]
Message-ID: <4947389D.1050708@cn.fujitsu.com> (raw)
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
next reply other threads:[~2008-12-16 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 5:11 Miao Xie [this message]
2008-12-16 6:26 ` Daisuke Nishimura
2008-12-16 8:25 ` Paul Menage
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4947389D.1050708@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®