From: Tejun Heo <tj@kernel.org>
To: Li Zefan <lizefan@huawei.com>
Cc: Cgroups <cgroups@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH v3 7/7] cpuset: fix to migrate mm correctly in a corner case
Date: Sun, 9 Jun 2013 08:49:30 -0700 [thread overview]
Message-ID: <20130609154930.GD2835@htj.dyndns.org> (raw)
In-Reply-To: <51B4480F.2050400@huawei.com>
On Sun, Jun 09, 2013 at 05:17:03PM +0800, Li Zefan wrote:
> Before moving tasks out of empty cpusets, update_tasks_nodemask()
> is called, which calls do_migrate_pages(xx, from, to). Then those
> tasks are moved to an ancestor, and do_migrate_pages() is called
> again.
>
> The first time: from = node_to_be_offlined, to = empty.
> The second time: from = empty, to = ancestor's nodemask.
>
> so looks like no pages will be migrated.
>
> Fix this by:
>
> - Don't call update_tasks_nodemask() on empty cpusets.
> - Pass cs->old_mems_allowed to do_migrate_pages().
>
> Signed-off-by: Li Zefan <lizefan@huawei.com>
> ---
> kernel/cpuset.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/cpuset.c b/kernel/cpuset.c
> index d1d6782..3cd68b8 100644
> --- a/kernel/cpuset.c
> +++ b/kernel/cpuset.c
> @@ -1563,9 +1563,16 @@ static void cpuset_attach(struct cgroup *cgrp, struct cgroup_taskset *tset)
> struct cpuset *mems_oldcs = effective_nodemask_cpuset(oldcs);
>
> mpol_rebind_mm(mm, &cpuset_attach_nodemask_to);
> - if (is_memory_migrate(cs))
> - cpuset_migrate_mm(mm, &mems_oldcs->mems_allowed,
> + if (is_memory_migrate(cs)) {
> + /*
> + * old_mems_allowed is the same with mems_allowed here,
> + * except if this task is being moved automatically due
> + * to hotplug, and in this case mems_allowed is empty
> + * and old_mems_allowed is the offlined node.
> + */
Wouldn't it be better if the above explain why rather than what?
> + cpuset_migrate_mm(mm, &mems_oldcs->old_mems_allowed,
> &cpuset_attach_nodemask_to);
> + }
> mmput(mm);
> }
>
> @@ -2155,7 +2162,7 @@ retry:
> * for empty cpuset to take on ancestor's cpumask.
> */
> if ((sane && cpumask_empty(cs->cpus_allowed)) ||
> - !cpumask_empty(&off_cpus))
> + (!cpumask_empty(&off_cpus) && !cpumask_empty(cs->cpus_allowed)))
> update_tasks_cpumask(cs, NULL);
No biggie but maybe we want briefly explain the conditions being tested?
Thanks.
--
tejun
next prev parent reply other threads:[~2013-06-09 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 9:14 [PATCH v3 0/7] cpuset: implement sane hierarchy behaviors Li Zefan
2013-06-09 9:14 ` [PATCH v3 1/7] cpuset: let hotplug propagation work wait for task attaching Li Zefan
2013-06-09 9:14 ` [PATCH v3 2/7] cpuset: remove async hotplug propagation work Li Zefan
2013-06-09 15:47 ` Tejun Heo
2013-06-09 9:15 ` [PATCH v3 3/7] cpuset: record old_mems_allowed in struct cpuset Li Zefan
2013-06-09 9:15 ` [PATCH v3 4/7] cpuset: introduce effective_{cpumask|nodemask}_cpuset() Li Zefan
2013-06-09 9:16 ` [PATCH v3 5/7] cpuset: allow to keep tasks in empty cpusets Li Zefan
2013-06-09 9:16 ` [PATCH v3 6/7] cpuset: allow to move tasks to " Li Zefan
2013-06-09 9:17 ` [PATCH v3 7/7] cpuset: fix to migrate mm correctly in a corner case Li Zefan
2013-06-09 15:49 ` Tejun Heo [this message]
2013-06-09 16:03 ` [PATCH v3 0/7] cpuset: implement sane hierarchy behaviors Tejun Heo
2013-06-13 7:04 ` Li Zefan
2013-06-13 17:49 ` Tejun Heo
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=20130609154930.GD2835@htj.dyndns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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®