[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080605090425.35c9ac0b.kamezawa.hiroyu@jp.fujitsu.com>
Date: Thu, 5 Jun 2008 09:04:25 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: nishimura@....nes.nec.co.jp
Cc: Daisuke Nishimura <d-nishimura@....biglobe.ne.jp>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
"balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com>,
"menage@...gle.com" <menage@...gle.com>,
"xemul@...nvz.org" <xemul@...nvz.org>,
"yamamoto@...inux.co.jp" <yamamoto@...inux.co.jp>
Subject: Re: [RFC][PATCH 2/2] memcg: hardwall hierarhcy for memcg
On Wed, 4 Jun 2008 21:32:35 +0900
Daisuke Nishimura <d-nishimura@....biglobe.ne.jp> wrote:
> Hi.
>
> > @@ -848,6 +937,8 @@ static int mem_cgroup_force_empty(struct
> > if (mem_cgroup_subsys.disabled)
> > return 0;
> >
> > + memcg_shrink_all(mem);
> > +
> > css_get(&mem->css);
> > /*
> > * page reclaim code (kswapd etc..) will move pages between
>
> Shouldn't it be called after verifying there remains no task
> in this group?
>
> If called via mem_cgroup_pre_destroy, it has been verified
> that there remains no task already, but if called via
> mem_force_empty_wrte, there may remain some tasks and
> this means many and many pages are swaped out, doesn't it?
>
you're right. I misunderstood where the number of children is checked.
Thanks,
-Kame
>
> Thanks,
> Daisuke Nishimura.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists