[lkml]   [2009]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC] [PATCH] Cgroup based OOM killer controller
    On Wed, 21 Jan 2009 16:38:21 +0530
    Nikanth Karthikesan <> wrote:

    > As Alan Cox suggested/wondered in this thread,
    > , this is a container group based approach
    > to override the oom killer selection without losing all the benefits of the
    > current oom killer heuristics and oom_adj interface.
    > It adds a tunable oom.victim to the oom cgroup. The oom killer will kill the
    > process using the usual badness value but only within the cgroup with the
    > maximum value for oom.victim before killing any process from a cgroup with a
    > lesser oom.victim number. Oom killing could be disabled by setting
    > oom.victim=0.
    > Signed-off-by: Nikanth Karthikesan <>

    Assume following
    - the usar can tell "which process should be killed at first"

    What is the difference between oom_adj and this cgroup to users ?
    If oom_adj is hard to use, making it simpler is a good way, I think.
    rather than adding new complication.

    It seems both of oom_adj and this cgroup will be hard-to-use functions
    for usual system administrators. But no better idea than using memcg
    and committing memory usage.


     \ /
      Last update: 2009-01-22 04:33    [W:0.030 / U:3.652 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site