linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp, linux-mm <linux-mm@kvack.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [RFC][PATCH 6/8] memcg: avoid oom during charge migration
Date: Fri, 25 Sep 2009 14:36:09 +0900	[thread overview]
Message-ID: <20090925143609.6cb8aaaf.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20090925135128.1d2e72e1.nishimura@mxp.nes.nec.co.jp>

On Fri, 25 Sep 2009 13:51:28 +0900, Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> On Fri, 25 Sep 2009 10:55:47 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > On Fri, 25 Sep 2009 10:44:09 +0900
> > Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> > 
> > > On Thu, 24 Sep 2009 16:34:40 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > > > On Thu, 24 Sep 2009 14:49:02 +0900
> > > > Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> > > > 
> > > > > This charge migration feature has double charges on both "from" and "to"
> > > > > mem_cgroup during charge migration.
> > > > > This means unnecessary oom can happen because of charge migration.
> > > > > 
> > > > > This patch tries to avoid such oom.
> > > > > 
> > > > > Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> > > > > ---
> > > > >  mm/memcontrol.c |   19 +++++++++++++++++++
> > > > >  1 files changed, 19 insertions(+), 0 deletions(-)
> > > > > 
> > > > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > > > index fbcc195..25de11c 100644
> > > > > --- a/mm/memcontrol.c
> > > > > +++ b/mm/memcontrol.c
> > > > > @@ -287,6 +287,8 @@ struct migrate_charge {
> > > > >  	unsigned long precharge;
> > > > >  };
> > > > >  static struct migrate_charge *mc;
> > > > > +static struct task_struct *mc_task;
> > > > > +static DECLARE_WAIT_QUEUE_HEAD(mc_waitq);
> > > > >  
> > > > >  static void mem_cgroup_get(struct mem_cgroup *mem);
> > > > >  static void mem_cgroup_put(struct mem_cgroup *mem);
> > > > > @@ -1317,6 +1319,7 @@ static int __mem_cgroup_try_charge(struct mm_struct *mm,
> > > > >  	while (1) {
> > > > >  		int ret = 0;
> > > > >  		unsigned long flags = 0;
> > > > > +		DEFINE_WAIT(wait);
> > > > >  
> > > > >  		if (mem_cgroup_is_root(mem))
> > > > >  			goto done;
> > > > > @@ -1358,6 +1361,17 @@ 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 migrating charge */
> > > > > +		if (mc_task && current != mc_task) {
> > > > 
> > > > Hmm, I like
> > > > 
> > > > ==
> > > > 	if (mc && mc->to == mem)
> > > > or
> > > > 	if (mc) {
> > > > 		if (mem is ancestor of mc->to)
> > > > 			wait for a while
> > > > ==
> > > > 
> > > > ?
> > > > 
> > > I think we cannot access safely to mc->to w/o cgroup_lock,
> > > and we cannot hold cgroup_lock in __mem_cgroup_try_charge.
> > > 
> > > And I think we need to check "current != mc_task" anyway to prevent
> > > the process itself which is moving a task from being stopped.
> > > (Thas's why I defined mc_task.)
> > 
> > I think
> > ==
> > static struct migrate_charge *mc;
> > ==
> > should be
> > ==
> > static struct migrate_charge mc;
> > ==
> > Then, mc_task can be a field of mc.
> > 
> > And, it seems ok "don't stop a task which is under migration" .
> > I agreed.
> > 
> Thank you for your suggestion.
> 
> I'm now thinking as follwing.
> 
> 
> struct move_charge {
> 	struct mem_cgroup *from;
> 	struct mem_cgroup *to;
> 	struct task_struct *target;	/* the target task being moved */
> 	struct task_struct *working;	/* a task moving the target task */
> 	unsigned long precharge;
> };
> static struct move_charge mc;
> 
> __mem_cgroup_try_charge
> {
> 	:
> 	if (mc.working && current != mc.working) {
> (1)		struct mem_cgroup *dest = mc.to;
> (2)		if (dest && css_is_ancestor(&dest->css, &mem_over_limit->css)
> 			continue;
> 	}
> 
> 	if (!nr_retries--) {
> 	:
> }
> 
> 
> But considering more, there is very small race that "dest" can be freed by rmdir
> between (1) or (2), IIUC.
> 
> Do you have any ideas ?
> 
IIUC, calling css_tryget() under rcu_read_lock() would work.

Thanks,
Daisuke Nishimura.

--
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>

  reply	other threads:[~2009-09-25  5:38 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  2:23 [RFC][EXPERIMENTAL][PATCH 0/8] memcg: migrate charge at task move Daisuke Nishimura
2009-09-17  2:24 ` [PATCH 1/8] memcg: introduce mem_cgroup_cancel_charge() Daisuke Nishimura
2009-09-17  4:12   ` KAMEZAWA Hiroyuki
2009-09-17  2:24 ` [PATCH 2/8] memcg: cleanup mem_cgroup_move_parent() Daisuke Nishimura
2009-09-17  4:15   ` KAMEZAWA Hiroyuki
2009-09-17  2:25 ` [PATCH 3/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-09-17  2:26 ` [PATCH 4/8] memcg: add interface to migrate charge Daisuke Nishimura
2009-09-17  4:20   ` KAMEZAWA Hiroyuki
2009-09-17  4:40     ` Daisuke Nishimura
2009-09-17  2:26 ` [PATCH 5/8] memcg: migrate charge of anon Daisuke Nishimura
2009-09-17  4:57   ` KAMEZAWA Hiroyuki
2009-09-17  5:56     ` Daisuke Nishimura
2009-09-17  6:25       ` KAMEZAWA Hiroyuki
2009-09-17 23:52     ` KOSAKI Motohiro
2009-09-17  2:27 ` [PATCH 6/8] memcg: migrate charge of shmem Daisuke Nishimura
2009-09-17  5:02   ` KAMEZAWA Hiroyuki
2009-09-17  2:28 ` [PATCH 7/8] memcg: migrate charge of swap Daisuke Nishimura
2009-09-17  5:25   ` KAMEZAWA Hiroyuki
2009-09-17  6:17     ` Daisuke Nishimura
2009-09-17  6:28       ` KAMEZAWA Hiroyuki
2009-09-17  2:29 ` [PATCH 8/8] memcg: avoid oom during charge migration Daisuke Nishimura
2009-09-17  7:01 ` [RFC][EXPERIMENTAL][PATCH 0/8] memcg: migrate charge at task move Daisuke Nishimura
2009-09-24  5:42   ` [RFC][PATCH 0/8] memcg: migrate charge at task move (24/Sep) Daisuke Nishimura
2009-09-24  5:43     ` [RFC][PATCH 1/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-09-24  6:33       ` KAMEZAWA Hiroyuki
2009-09-24 23:39         ` Daisuke Nishimura
2009-09-24  5:44     ` [RFC][PATCH 2/8] memcg: introduce mem_cgroup_cancel_charge() Daisuke Nishimura
2009-09-24  5:46     ` [RFC][PATCH 3/8] memcg: cleanup mem_cgroup_move_parent() Daisuke Nishimura
2009-09-24  6:37       ` KAMEZAWA Hiroyuki
2009-09-24  6:54         ` Daisuke Nishimura
2009-09-24  5:47     ` [RFC][PATCH 4/8] memcg: add interface to migrate charge Daisuke Nishimura
2009-09-24  6:54       ` KAMEZAWA Hiroyuki
2009-09-24 23:39         ` Daisuke Nishimura
2009-09-24  5:48     ` [RFC][PATCH 5/8] memcg: migrate charge of mapped page Daisuke Nishimura
2009-09-24  7:22       ` KAMEZAWA Hiroyuki
2009-09-24  8:00         ` Daisuke Nishimura
2009-09-25  0:28           ` Daisuke Nishimura
2009-09-25  0:49             ` KAMEZAWA Hiroyuki
2009-09-24  5:49     ` [RFC][PATCH 6/8] memcg: avoid oom during charge migration Daisuke Nishimura
2009-09-24  7:34       ` KAMEZAWA Hiroyuki
2009-09-25  1:44         ` Daisuke Nishimura
2009-09-25  1:55           ` KAMEZAWA Hiroyuki
2009-09-25  4:51             ` Daisuke Nishimura
2009-09-25  5:36               ` Daisuke Nishimura [this message]
2009-09-25  5:52                 ` KAMEZAWA Hiroyuki
2009-09-24  5:49     ` [RFC][PATCH 7/8] memcg: migrate charge of swap Daisuke Nishimura
2009-09-24  5:50     ` [RFC][PATCH 8/8] memcg: migrate charge of shmem swap Daisuke Nishimura
2009-09-24  7:41       ` KAMEZAWA Hiroyuki
2009-09-25  0:28         ` Daisuke Nishimura

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=20090925143609.6cb8aaaf.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --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