lkml.org 
[lkml]   [2001]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] Prevent OOM from killing init

    On Thu, 22 Mar 2001, Alan Cox wrote:

    > One of the things that we badly need to resurrect for 2.5 is the
    > beancounter work which would let you reasonably do things like
    > guaranteed Oracle a certain amount of the machine, or restrict all
    > the untrusted users to a total of 200Mb hard limit between them etc

    This would improve Linux reliability but it could be much better with
    added *optional* non-overcommit (most other OS also support this, also
    that's the default mostly [please no, "but it deadlocks" because it's
    not true, they also kill processes (Solaris, etc)]), reserved superuser
    memory (ala Solaris, True64, etc when OOM in non-overcommit, users
    complain and superuser acts, not the OS killing their tasks) and
    superuser *advisory* OOM killer [there was patch for this before], I
    think in the last area Linux is already more ahead than others at
    present.

    About the "use resource limits!". Yes, this is one solution. The
    *expensive* solution (admin time, worse resource utilization, etc).
    Others make it cheaper mixing with the above ones.

    Szaka

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:17    [W:2.337 / U:0.224 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site