lkml.org 
[lkml]   [2002]   [May]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Memory management in Kernel 2.4.x
From
Date
On Mon, 2002-05-27 at 22:22, H. Peter Anvin wrote:
> Followup to: <1022513156.1126.289.camel@irongate.swansea.linux.org.uk>
> By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
> In newsgroup: linux.dev.kernel
> >
> > On a -ac kernel with mode 2 or 3 set for overcommit you have to run out
> > of kernel resources to hang the box. It won't go OOM because it can't.
> > That wouldn't be a VM bug but a leak or poor handling of kernel
> > allocations somewhere. Sadly the changes needed to do that (beancounter
> > patch) were things Linus never accepted for 2.4
> >
>
> Well, if you can't fork a new process because that would push you into
> overcommit, then you usually can't actually do anything useful on the
> machine.

Thats actually easy to deal with and on my list for modes 4 and 5 (2 and
3 with root granted a reserved fraction)

-
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:26    [W:0.116 / U:0.864 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site