lkml.org 
[lkml]   [2008]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC] How to handle the rules engine for cgroups
    KAMEZAWA Hiroyuki wrote:
    > On Tue, 1 Jul 2008 15:11:26 -0400
    > Vivek Goyal <vgoyal@redhat.com> wrote:
    >
    >> Hi,
    >>
    >> While development is going on for cgroup and various controllers, we also
    >> need a facility so that an admin/user can specify the group creation and
    >> also specify the rules based on which tasks should be placed in respective
    >> groups. Group creation part will be handled by libcg which is already
    >> under development. We still need to tackle the issue of how to specify
    >> the rules and how these rules are enforced (rules engine).
    >>
    >
    > A different topic.
    >
    > Recently I'm interested in "How to write userland daemon program
    > to control group subsystem." To implement that effectively, we need
    > some notifier between user <-> kernel.
    >
    > Can we use "inotify" to catch changes in cgroup (by daemon program) ?
    >
    > For example, create a new file under memory cgroup
    > ==
    > /opt/memory_cgroup/group_A/notify_at_memory_reach_limit
    > ==
    > And a user watches the file by inotify.
    > The kernel modify modified-time of notify_at_memory_reach_limit file and call
    > fs/notify_user.c::notify_change() against this inode. He can catchthe event
    > by inotify.

    Won't the time latency be an issue (time between exceeding the limit and the
    user space being notified?). Since the notification does not use user memory at
    the moment (it will not stress the limits futher :)), provided the notification
    handler is not running under the group that has exceeded its limit. Do we expect
    the user space application to ACK that it's seen the notification? We could use
    a netlink channel as well (in the case that we need two way communication).

    I would prefer to notify on memory.failcnt, if we do use this interface.

    > (I think he can also catch removal of this file, etc...)
    >
    > Is there some difficulty or problem ? (I'm sorry if we can do this now.)



    --
    Warm Regards,
    Balbir Singh
    Linux Technology Center
    IBM, ISTL


    \
     
     \ /
      Last update: 2008-07-18 18:41    [W:0.025 / U:0.796 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site