Messages in this thread | | | Date | Mon, 12 Sep 2011 19:31:17 +0900 | From | KAMEZAWA Hiroyuki <> | Subject | Re: [PATCH v2 6/9] per-cgroup tcp buffers control |
| |
On Fri, 9 Sep 2011 09:01:32 -0300 Glauber Costa <glommer@parallels.com> wrote:
> On 09/09/2011 12:12 AM, KAMEZAWA Hiroyuki wrote: > > On Wed, 7 Sep 2011 01:23:16 -0300 > > Glauber Costa<glommer@parallels.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@parallels.com> > >> CC: David S. Miller<davem@davemloft.net> > >> CC: Hiroyouki Kamezawa<kamezawa.hiroyu@jp.fujitsu.com> > >> CC: Eric W. Biederman<ebiederm@xmission.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
| |