On 04/30/2013 03:17 AM, Glauber Costa wrote:
On 04/30/2013 01:48 PM, Kir Kolyshkin wrote:
On 04/29/2013 10:12 PM, Glauber Costa wrote:
The kernel memory controller cannot flip states from unlimited to
limited if
there are already tasks in it. Therefore, we always have to run with
*some*
value
The kernel memory controller cannot flip states from unlimited to limited if
there are already tasks in it. Therefore, we always have to run with *some*
value of kmem enabled. If we don't do it, we can't start unlimited and then use
the set command to set any beancounters. We write the maximum
On 04/29/2013 10:12 PM, Glauber Costa wrote:
The kernel memory controller cannot flip states from unlimited to limited if
there are already tasks in it. Therefore, we always have to run with *some*
value of kmem enabled. If we don't do it, we can't start unlimited and then use
the set command
On 04/30/2013 01:48 PM, Kir Kolyshkin wrote:
On 04/29/2013 10:12 PM, Glauber Costa wrote:
The kernel memory controller cannot flip states from unlimited to
limited if
there are already tasks in it. Therefore, we always have to run with
*some*
value of kmem enabled. If we don't do it, we
