Re: Killing/balancing processes when overcommited

Helge Hafting (helgehaf@aitel.hist.no)
Mon, 16 Sep 2002 09:29:47 +0200


Rik van Riel wrote:

> If you kill the process that requests memory, the sequence often
> goes as follows:
>
> 1) memory is exhausted
>
> 2) the network driver can't allocate memory and
> spits out a message
>
> 3) syslogd and/or klogd get killed
>
> Clearly you want to be a bit smarter about which process to kill.

Ill-implemented klogd/syslogd. Pre-allocating a little memory
is one way to go, or drop messages until allocation
becomes possible again. Then log a complaint about
messages missing due to a temporary OOM.

Helge Hafting
-
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/