[PATCH 1/1] Memory usage limit notification addition to memcg
Vladislav D. Buzov
vbuzov at embeddedalley.com
Mon Jul 13 14:21:16 PDT 2009
KAMEZAWA Hiroyuki wrote:
> 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.)
It still does not answer the question how to select the number of events
before/between sending the notification.
The idea behind the notification feature is to let user applications
know immediately when a low memory condition occurs (the threshold is
exceeded). So that they can take action to free unused memory before the
OS is involved to handle that (OOM-kill, reclaiming pages).
As far as I understand the reason why you would like to add a delay
between sending notifications is to let user applications some time to
free memory. This is not required by design of the notification feature
because the notification is sent only if someone listening for it.
Typical application will subscribe for low-memory notification, receive
it, handle and then subscribe again. So, even if low memory conditions
keep occurring in mean time, the notification will not be fired. If it
happens again after the user application freed some memory the
application will be immediately notified.
>>> 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".
I'm going to send another patch soon where I added threshold feature to
the Resource Counter. It's going to address all concerns about data
More information about the Containers