[lkml]   [2002]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Killing/balancing processes when overcommited
On Mon, 16 Sep 2002, Helge Hafting wrote:
> Rik van Riel wrote:
> > 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.

No. This has absolutely nothing to do with it.

In this case, "allocating memory" simply means that klogd/syslogd
page faults on something it already allocated, say a piece of the
executable or a swapped-out buffer.

Simple page faults like this can also trigger an OOM-killing.

Bravely reimplemented by the knights who say "NIH".

Spamtraps of the month:

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.102 / U:4.184 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site