From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
nishimura@mxp.nes.nec.co.jp, balbir@linux.vnet.ibm.com,
lizf@cn.fujitsu.com, menage@google.com
Subject: Re: [PATCH 0/2] memcg: cgroup fix rmdir hang
Date: Fri, 26 Jun 2009 08:29:56 +0900 [thread overview]
Message-ID: <20090626082956.a90335db.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090625142809.ac6b7b85.akpm@linux-foundation.org>
On Thu, 25 Jun 2009 14:28:09 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 23 Jun 2009 16:07:20 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> > previous discussion was this => http://marc.info/?t=124478543600001&r=1&w=2
> >
> > This patch tries to fix problem as
> > - rmdir can sleep very very long if swap entry is shared between multiple
> > cgroups
> >
> > Now, cgroup's rmdir path does following
> >
> > ==
> > again:
> > check there are no tasks and children group.
> > call pre_destroy()
> > check css's refcnt
> > if (refcnt > 0) {
> > sleep until css's refcnt goes down to 0.
> > goto again
> > }
> > ==
> >
> > Unfortunately, memory cgroup does following at charge.
> >
> > css_get(&memcg->css)
> > ....
> > charge(memcg) (increase USAGE)
> > ...
> > And this "memcg" is not necessary to include the caller, task.
> >
> > pre_destroy() tries to reduce memory usage until USAGE goes down to 0.
> > Then, there is a race that
> > - css's refcnt > 0 (and memcg's usage > 0)
> > - rmdir() caller sleeps until css->refcnt goes down 0.
> > - But to make css->refcnt be 0, pre_destroy() should be called again.
> >
> > This patch tries to fix this in asyhcnrounos way (i.e. without big lock.)
> > Any comments are welcome.
> >
>
> Do you believe that these fixes should be backported into 2.6.30.x?
Yes, I think so. (If it's easy)
To be honest:
To cause the problem,
- swap cgroup should be shared between cgroup.
- rmdir should be called in critical chance.
Considering usual usage of cgroup is "container", there will be no share of swap
in typical users. But, 2.6.30 can be a base kernel of a major distro. So,
I hope this in 2.6.30 if we have no difficulties.
Thanks,
-Kame
--
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-06-25 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 7:07 KAMEZAWA Hiroyuki
2009-06-23 7:08 ` [PATCH 1/2] " KAMEZAWA Hiroyuki
2009-06-24 4:05 ` Daisuke Nishimura
2009-06-25 21:50 ` Andrew Morton
2009-06-26 0:14 ` KAMEZAWA Hiroyuki
2009-06-23 7:10 ` [PATCH 2/2] memcg: wakeup rmdir waiter if necessary KAMEZAWA Hiroyuki
2009-06-25 21:28 ` [PATCH 0/2] memcg: cgroup fix rmdir hang Andrew Morton
2009-06-25 23:29 ` KAMEZAWA Hiroyuki [this message]
2009-06-26 5:10 ` [PATCH] " KAMEZAWA Hiroyuki
2009-06-26 6:00 ` Daisuke Nishimura
2009-06-29 4:10 ` Daisuke Nishimura
2009-06-26 20:16 ` Paul Menage
2009-06-28 23:50 ` KAMEZAWA Hiroyuki
2009-06-28 23:56 ` 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=20090626082956.a90335db.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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