Messages in this thread | | | Subject | Re: Protecting processes from the OOM killer | From | James Antill <> | Date | 28 Feb 2003 17:13:56 -0500 |
| |
Dan Kegel <dank@kegel.com> writes:
> Alan Cox wrote: > > On Fri, 2003-02-28 at 01:21, Dan Kegel wrote: > > > > Everything else is armwaving "works half the time" stuff. By the time > > the OOM kicks in the game is already over. > > Even with overcommit disallowed, the OOM killer is going to run > when my users try to run too big a job, so I would still like > the OOM killer to behave "well".
If OOM is called you've overcommitted memory, so this isn't true ... no overcommit == NULL from malloc() etc.
-- # James Antill -- james@and.org :0: * ^From: .*james@and\.org /dev/null - 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/
| |