lkml.org 
[lkml]   [2002]   [Jul]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH] strict VM overcommit for stock 2.4
    From
    Date
    On Fri, 2002-07-19 at 00:30, Szakacsits Szabolcs wrote:

    > *However* distinguishing root and non-root users also in strict VM
    > overcommit would make a significant difference for general purpose
    > systems, this was always my point.
    >
    > Can you see the non-orthogonality now?

    Nope, I still disagree and there is no point going back and forth.

    We both agree that there are situations where both resource accounting
    (or some sort of root-protection like you want) and strict overcommit is
    required.

    I contend there are situations where only one or the other is needed.

    More importantly, I argue the two things should be kept separate.
    Putting some root safety net into strict accounting is a hack (how much
    of a net? etc.). You want to keep users from ruining things - get
    per-user resource limits. You want to keep the machine from
    overcommiting memory and thus not OOMing? Get strict accounting. You
    want both? Use both.

    I provided the first piece.

    Robert Love

    -
    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:27    [W:0.048 / U:60.184 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site