lkml.org 
[lkml]   [2008]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC][PATCH 0/2] memcg: hierarchy support (v3)
    On Wed, 4 Jun 2008 01:59:32 -0700
    "Paul Menage" <menage@google.com> wrote:

    > Hi Kame,
    >
    > I like the idea of keeping the kernel simple, and moving more of the
    > intelligence to userspace.
    >
    thanks.

    > It may need the kernel to expose a bit more in the way of VM details,
    > such as memory pressure, OOM notifications, etc, but as long as
    > userspace can respond quickly to memory imbalance, it should work
    > fine. We're doing something a bit similar using cpusets and fake NUMA
    > at Google - the principle of juggling memory between cpusets is the
    > same, but the granularity is much worse :-)
    >
    yes, next problem is adding interfaces. but we have to investigate
    what is principal.


    > On Tue, Jun 3, 2008 at 9:58 PM, KAMEZAWA Hiroyuki
    > <kamezawa.hiroyu@jp.fujitsu.com> wrote:
    > > - supported hierarchy_model parameter.
    > > Now, no_hierarchy and hardwall_hierarchy is implemented.
    >
    > Should we try to support hierarchy and non-hierarchy cgroups in the
    > same tree? Maybe we should just enforce the restrictions that:
    >
    > - the hierarchy mode can't be changed on a cgroup if you have children
    > or any non-zero usage/limit
    > - a cgroup inherits its parent's hierarchy mode.
    >
    Ah, my patch does it (I think). explanation is bad.

    - mem cgroup's mode can be changed against ROOT node which has no children.
    - a child inherits parent's mode.

    Thanks,
    -Kame




    \
     
     \ /
      Last update: 2008-06-04 11:13    [W:0.028 / U:126.040 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site