linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pavel Emelyanov <xemul@openvz.org>,
	Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>
Subject: Re: [RFC][PATCH 5/4] memcg: don't call res_counter_uncharge when obsolete
Date: Thu, 15 Jan 2009 13:54:05 +0900	[thread overview]
Message-ID: <20090115135405.a15a6877.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090115044557.GG21516@balbir.in.ibm.com>

On Thu, 15 Jan 2009 10:15:57 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:

> * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-01-15 13:41:14]:
> 
> > On Thu, 15 Jan 2009 09:47:50 +0530
> > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > 
> > > * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-01-15 12:24:16]:
> > 
> > > > But I don't like -EBUSY ;)
> > > > 
> > > > When rmdir() returns -EBUSY even if there are no (visible) children and tasks,
> > > > our customer will take kdump and send it to me "please explain this kernel bug"
> > > > 
> > > > I'm sure it will happen ;)
> > > >
> > > 
> > > OK, but memory.stat can show why the group is busy and with
> > > move_to_parent() such issues should not occur right? I'll relook at
> > > the code. Thanks for your input.
> > > 
> > 
> > There was a design choice at swap_cgroup.
> > 
> > At rmdir, there may be used swap entry in memcg. (mem->memsw.usage can be > 0)
> >   1. update all records in swap cgroup
> >   2. just ignore account from swap, we can treat then at swap-in.
> > 
> > I implemented "2" by refcnt.
> > 
> > To do "1", we have to scan all used swap_cgroup but I don't want to scan all
> > swap_cgroup entry at rmdir. It's heavy job.
> > (*) To reduce memory usage by swap_cgroup, swap_cgroup just have a pointer to memcg
> > (**) I implemented swap_cgroup as statically allocated array because I don't want
> >     any dynamic memory allocation at swap-out and want to avoid unnecessary memory
> >     usage.
> 
> Fair enough, but I don't like that we don't have any checks for
> 
> If parent still has children, parent should not go away. The
> problem that Daisuke-San is seeing.
> 
The parent has "no children" in cgroup layer. It just has children in
"memory subsys" layer.

It's better to add mem_cgroup_get()/put agaisnt the parent at create()/destroy().
I'm now preparing a patch.

-Kame


> -- 
> 	Balbir
> 

--
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-01-15  4:55 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  9:45 [PATCH -rc] some fixes for memcg Daisuke Nishimura
2009-01-13  9:47 ` [PATCH 1/4] memcg: fix mem_cgroup_get_reclaim_stat_from_page Daisuke Nishimura
2009-01-13  9:48 ` [PATCH 2/4] memcg: fix error path of mem_cgroup_move_parent Daisuke Nishimura
2009-01-13  9:49 ` [PATCH 3/4] memcg: fix hierarchical reclaim Daisuke Nishimura
2009-01-13  9:50 ` [PATCH 4/4] memcg: make oom less frequently Daisuke Nishimura
2009-01-14  8:51 ` [RFC][PATCH 5/4] memcg: don't call res_counter_uncharge when obsolete Daisuke Nishimura
2009-01-14 13:43   ` KAMEZAWA Hiroyuki
2009-01-15  1:03     ` Daisuke Nishimura
2009-01-15  2:00       ` KAMEZAWA Hiroyuki
2009-01-15  2:14         ` Daisuke Nishimura
2009-01-15  4:38           ` Daisuke Nishimura
2009-01-15  5:14             ` KAMEZAWA Hiroyuki
2009-01-15  5:49               ` Balbir Singh
2009-01-15  6:39             ` KAMEZAWA Hiroyuki
2009-01-15  7:45             ` [RFC][PATCH] memcg: get/put parents at create/free Daisuke Nishimura
2009-01-15  7:54               ` KAMEZAWA Hiroyuki
2009-01-15  8:13                 ` Daisuke Nishimura
2009-01-15  8:23                   ` KAMEZAWA Hiroyuki
2009-01-15  8:51                     ` Daisuke Nishimura
2009-01-15  9:10                       ` KAMEZAWA Hiroyuki
2009-01-16  1:50                         ` [BUGFIX][PATCH] " Daisuke Nishimura
2009-01-16  2:12                           ` Andrew Morton
2009-01-16  2:17                             ` KAMEZAWA Hiroyuki
2009-01-16  2:25                               ` Daisuke Nishimura
2009-01-16  4:22                           ` Daisuke Nishimura
2009-01-16  4:31                             ` KAMEZAWA Hiroyuki
2009-01-14 13:55   ` [RFC][PATCH 5/4] memcg: don't call res_counter_uncharge when obsolete Balbir Singh
2009-01-15  2:48     ` KAMEZAWA Hiroyuki
2009-01-15  3:08       ` KAMEZAWA Hiroyuki
2009-01-15  3:24     ` KAMEZAWA Hiroyuki
2009-01-15  4:17       ` Balbir Singh
2009-01-15  4:41         ` KAMEZAWA Hiroyuki
2009-01-15  4:45           ` Balbir Singh
2009-01-15  4:54             ` KAMEZAWA Hiroyuki [this message]
2009-01-15  4:52         ` KAMEZAWA Hiroyuki
2009-01-15  5:17           ` Balbir Singh
2009-01-15  5:27             ` 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=20090115135405.a15a6877.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 \
    --cc=xemul@openvz.org \
    /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