lkml.org 
[lkml]   [2005]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Resource limits
    On 9/26/05, Roger Heflin <rheflin@atipa.com> wrote:
    >
    > While talking about limits, one of my customers report that if
    > they set "ulimit -d" to be say 8GB, and then a program goes and
    > attempts to allocate 16GB (in one shot), that the process will
    > hang on the 16GB allocate as the machine does not have enough
    > memory+swap to handle this, the process is at this time unkillable,
    > the customers method to kill the process is to send the process
    > a kill signal, and then create enough swap to be able to meet
    > the request, after the request is filled the process terminates.
    >
    > It would seem that the best thing to do would be to abort on
    > allocates that will by themselves exceed the limit.
    >
    > This was a custom version of a earlier version of the 2.6 kernel,
    > I would bet that this has not changed in quite a while.
    >
    > Roger

    It's simple. Set /proc/sys/vm/overcommit_memory to 2 (iirc) to get
    arround this `bug' .
    --
    Coywolf Qi Hunt
    http://sosdg.org/~coywolf/
    -
    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-09-27 05:52    [W:0.022 / U:32.764 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site