[PATCH 1/1] Memory usage limit notification addition to memcg

KAMEZAWA Hiroyuki kamezawa.hiroyu at jp.fujitsu.com
Sun Jul 12 17:52:09 PDT 2009

On Wed, 08 Jul 2009 18:43:48 -0700
"Vladislav D. Buzov" <vbuzov at embeddedalley.com> wrote:

> KAMEZAWA Hiroyuki wrote:

> > 2 points.
> >  - Do we have to check this always we account ?
> >   
> What are the options? Every N pages? How to select N?
I think you can reuse Balbir's softlimit event counter. (see v9.)

> > If this is true, "set limit" should be checked to guarantee this.
> > plz allow minus this for avoiding mess.
> Setting the memory controller cgroup limit and the notification
> threshold are two separate operations. There isn't any "mess," just some
> validation testing for reporting back to the source of the request. When
> changing the memory controller limit, we ensure the threshold limit is
> never allowed "negative." At most, the threshold limit will be equal the
> memory controller cgroup limit. Otherwise, the arithmetic and
> conditional tests during the operational part of the software becomes
> more complex, which we don't want.
Hmm, then, plz this interface put under "set_limit_mutex".


More information about the Containers mailing list