[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OT] Linux Out-Of-Memory Killer
|
From: |
Marc Herbert |
|
Subject: |
Re: [OT] Linux Out-Of-Memory Killer |
|
Date: |
Thu, 04 Nov 2010 09:47:27 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc13 Thunderbird/3.1.6 |
Le 03/11/2010 18:50, Bob Proulx a écrit :
> Marc Herbert wrote:
>> I suggest that Linux kids do not try this at home: the OutOfMemory killer
>> killed a few random processes of mine!
>
> Off-Topic for this mailing list but if so then you should configure
> your Linux kernel to avoid memory overcommit. I have previously
> ranted about this
The (controlled) randomness of the OOM killer looks indeed really
weird and scary. But it looks a bit less weird when you think about
what happens when you disable the killer and run out of memory: which
process(es) will get malloc() and fork() errors then? The answer is
STILL NOT deterministic!
Without going into further details since this is really off-topic: no
one should assume that Linux developers smoke crack and that disabling
the OOM killer is a simple solution to a simple problem. It is not so
simple, you unfortunately have to do your homework.