[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20110912193117.d8f360f9.kamezawa.hiroyu@jp.fujitsu.com>
Date: Mon, 12 Sep 2011 19:31:17 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: Glauber Costa <glommer@...allels.com>
Cc: <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<containers@...ts.osdl.org>, <netdev@...r.kernel.org>,
<xemul@...allels.com>, "David S. Miller" <davem@...emloft.net>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH v2 6/9] per-cgroup tcp buffers control
On Fri, 9 Sep 2011 09:01:32 -0300
Glauber Costa <glommer@...allels.com> wrote:
> On 09/09/2011 12:12 AM, KAMEZAWA Hiroyuki wrote:
> > On Wed, 7 Sep 2011 01:23:16 -0300
> > Glauber Costa<glommer@...allels.com> wrote:
> >
> >> With all the infrastructure in place, this patch implements
> >> per-cgroup control for tcp memory pressure handling.
> >>
> >> Signed-off-by: Glauber Costa<glommer@...allels.com>
> >> CC: David S. Miller<davem@...emloft.net>
> >> CC: Hiroyouki Kamezawa<kamezawa.hiroyu@...fujitsu.com>
> >> CC: Eric W. Biederman<ebiederm@...ssion.com>
> >
> > Hmm, then, kmem_cgroup.c is just a caller of plugins implemented
> > by other components ?
>
> Kame,
>
> Refer to my discussion with Greg. How would you feel about it being
> accounted to a single "kernel memory" limit in memcg?
>
Hmm, it's argued that 'cgroup is hard to use, it's difficult!!!'.
Then, if implementation is clean, I think it may be good to add
kmem limit to memcg.
Your and Greg's idea is to have
memory.kmem_limit_in_bytes
?
Thanks,
-Kame
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists