>> > I am not convinced this is the best way to solve the problem, or that
>> > we must even merge it. Yes, it is a problem, but that is just a hack.
>> > Can we do better?
>> >
>> > Dhaval
>> >
>> >
>> yes, the solution seems not optimal. Is it better to do the check in function
>> cg_set_control
- Original Message -
> From: "Weng Meiling"
> To: "Dhaval Giani"
> Cc: "Ivana Varekova" , "Libcg Development list"
> , "libo chen"
> , "Balbir Singh"
> Sent: Friday, August 23, 2013 3:10:31 AM
> Sub
t;>> Sent: Friday, August 2, 2013 10:27:00 AM
>>> Subject: [Libcg-devel] [PATCH]add the value check before set the control
>>> file value
>>>
>>>
>>> From: Weng Meiling
>>>
>>> When we use memory subsystem, the memory.oom_cont
On Thu, Aug 22, 2013 at 8:32 AM, Ivana Varekova wrote:
>
>
> - Original Message -
>> From: "Weng Meiling"
>> To: libcg-devel@lists.sourceforge.net
>> Cc: "libo chen"
>> Sent: Friday, August 2, 2013 10:27:00 AM
>> Subject: [Lib
- Original Message -
> From: "Weng Meiling"
> To: libcg-devel@lists.sourceforge.net
> Cc: "libo chen"
> Sent: Friday, August 2, 2013 10:27:00 AM
> Subject: [Libcg-devel] [PATCH]add the value check before set the control
> file value
>
From: Weng Meiling
When we use memory subsystem, the memory.oom_control value we get like
this:
oom_kill_disable 0
under_oom 0
but we set the value just by writing a value(0 or 1) like this:
#echo 1 > memory.oom_control
so setting the value memory.oom_control by cgset --copy-from or
the conf
