From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>
Subject: Re: [PATCH -mmotm 6/8] memcg: avoid oom during moving charge
Date: Tue, 15 Dec 2009 11:05:39 +0900 [thread overview]
Message-ID: <20091215110539.f6f5d4b0.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20091214152443.05871e9c.nishimura@mxp.nes.nec.co.jp>
On Mon, 14 Dec 2009 15:24:43 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> This move-charge-at-task-migration feature has extra charges on "to"(pre-charges)
> and "from"(left-over charges) during moving charge. This means unnecessary oom
> can happen.
>
> This patch tries to avoid such oom.
>
> Changelog: 2009/12/14
> - instead of continuing to charge by busy loop, make use of waitq.
> Changelog: 2009/12/04
> - take account of "from" too, because we uncharge from "from" at once in
> mem_cgroup_clear_mc(), so left-over charges exist during moving charge.
> - check use_hierarchy of "mem_over_limit", instead of "to" or "from"(bugfix).
>
> Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
seems nice...but I wonder can this be generic one ? like...
"If someone goes into oom or a task is moved, all other charges should wait.."
Hm, but it may sound overkill ;), sorry.
Thanks,
-Kame
> ---
> mm/memcontrol.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++--
> 1 files changed, 52 insertions(+), 2 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 8d86a20..9c8719a 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -253,6 +253,9 @@ struct move_charge_struct {
> struct mem_cgroup *to;
> unsigned long precharge;
> unsigned long moved_charge;
> + struct task_struct *moving_task; /* a task moving charges */
> + wait_queue_head_t waitq; /* a waitq for other context */
> + /* not to cause oom */
> };
> static struct move_charge_struct mc;
>
> @@ -1509,6 +1512,48 @@ static int __mem_cgroup_try_charge(struct mm_struct *mm,
> if (mem_cgroup_check_under_limit(mem_over_limit))
> continue;
>
> + /* try to avoid oom while someone is moving charge */
> + if (mc.moving_task && current != mc.moving_task) {
> + struct mem_cgroup *from, *to;
> + bool do_continue = false;
> + /*
> + * There is a small race that "from" or "to" can be
> + * freed by rmdir, so we use css_tryget().
> + */
> + rcu_read_lock();
> + from = mc.from;
> + to = mc.to;
> + if (from && css_tryget(&from->css)) {
> + if (mem_over_limit->use_hierarchy)
> + do_continue = css_is_ancestor(
> + &from->css,
> + &mem_over_limit->css);
> + else
> + do_continue = (from == mem_over_limit);
> + css_put(&from->css);
> + }
> + if (!do_continue && to && css_tryget(&to->css)) {
> + if (mem_over_limit->use_hierarchy)
> + do_continue = css_is_ancestor(
> + &to->css,
> + &mem_over_limit->css);
> + else
> + do_continue = (to == mem_over_limit);
> + css_put(&to->css);
> + }
> + rcu_read_unlock();
> + if (do_continue) {
> + DEFINE_WAIT(wait);
> + prepare_to_wait(&mc.waitq, &wait,
> + TASK_INTERRUPTIBLE);
> + /* moving charge context might have finished. */
> + if (mc.moving_task)
> + schedule();
> + finish_wait(&mc.waitq, &wait);
> + continue;
> + }
> + }
> +
> if (!nr_retries--) {
> if (oom) {
> mem_cgroup_out_of_memory(mem_over_limit, gfp_mask);
> @@ -3385,7 +3430,8 @@ mem_cgroup_create(struct cgroup_subsys *ss, struct cgroup *cont)
> INIT_WORK(&stock->work, drain_local_stock);
> }
> hotcpu_notifier(memcg_stock_cpu_callback, 0);
> -
> + mc.waitq = (wait_queue_head_t)
> + __WAIT_QUEUE_HEAD_INITIALIZER(mc.waitq);
> } else {
> parent = mem_cgroup_from_cont(cont->parent);
> mem->use_hierarchy = parent->use_hierarchy;
> @@ -3645,6 +3691,8 @@ static void mem_cgroup_clear_mc(void)
> }
> mc.from = NULL;
> mc.to = NULL;
> + mc.moving_task = NULL;
> + wake_up_all(&mc.waitq);
> }
>
> static int mem_cgroup_can_attach(struct cgroup_subsys *ss,
> @@ -3670,9 +3718,11 @@ static int mem_cgroup_can_attach(struct cgroup_subsys *ss,
> VM_BUG_ON(mc.to);
> VM_BUG_ON(mc.precharge);
> VM_BUG_ON(mc.moved_charge);
> + VM_BUG_ON(mc.moving_task);
> mc = (struct move_charge_struct) {
> .from = from, .to = mem, .precharge = 0,
> - .moved_charge = 0
> + .moved_charge = 0,
> + .moving_task = current, .waitq = mc.waitq
> };
>
> ret = mem_cgroup_precharge_mc(mm);
> --
> 1.5.6.1
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-12-15 2:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 6:17 [PATCH -mmotm 0/8] memcg: move charge at task migration (14/Dec) Daisuke Nishimura
2009-12-14 6:18 ` [PATCH -mmotm 1/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-12-14 6:19 ` [PATCH -mmotm 2/8] cgroup: introduce coalesce css_get() and css_put() Daisuke Nishimura
2009-12-16 2:14 ` Paul Menage
2009-12-14 6:20 ` [PATCH -mmotm 3/8] memcg: add interface to move charge at task migration Daisuke Nishimura
2009-12-14 6:21 ` [PATCH -mmotm 4/8] memcg: move charges of anonymous page Daisuke Nishimura
2009-12-14 6:23 ` [PATCH -mmotm 5/8] memcg: improve performance in moving charge Daisuke Nishimura
2009-12-14 6:24 ` [PATCH -mmotm 6/8] memcg: avoid oom during " Daisuke Nishimura
2009-12-15 2:05 ` KAMEZAWA Hiroyuki [this message]
2009-12-14 6:25 ` [PATCH -mmotm 7/8] memcg: move charges of anonymous swap Daisuke Nishimura
2009-12-14 6:26 ` [PATCH -mmotm 8/8] memcg: improbe performance in moving swap charge Daisuke Nishimura
2009-12-15 3:30 ` [PATCH -mmotm 0/8] memcg: move charge at task migration (14/Dec) Balbir Singh
2009-12-15 4:14 ` Daisuke Nishimura
2009-12-17 7:00 ` Daisuke Nishimura
2009-12-17 7:27 ` KAMEZAWA Hiroyuki
2009-12-21 5:31 [PATCH -mmotm 0/8] memcg: move charge at task migration (21/Dec) Daisuke Nishimura
2009-12-21 5:37 ` [PATCH -mmotm 6/8] memcg: avoid oom during moving charge Daisuke Nishimura
2009-12-21 7:03 ` KAMEZAWA Hiroyuki
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=20091215110539.f6f5d4b0.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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