Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: Memory management in Kernel 2.4.x | Date | 27 May 2002 14:22:22 -0700 |
| |
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.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - 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/
| |