Thread (10 messages) 10 messages, 7 authors, 2001-03-24

Re: [PATCH] Prevent OOM from killing init

From: Rik van Riel <hidden>
Date: 2001-03-24 06:42:49
Also in: lkml

On Fri, 23 Mar 2001, Szabolcs Szakacsits wrote:
When I ported your OOM killer to 2.2.x and integrated it into the
'reserved root memory' [*] patch, during intensive testing I found two
cases when init was killed. It happened on low-end machines and when
OOM killer wasn't triggered so init was killed in the page fault
handler. The later was also one of the reasons I replaced the "random"
OOM killer in page fault handler with yours [so there is only one OOM
killer].
Good idea, we should do this for 2.4.  I cannot remember
reading an email from you about this, it's quite possible
I just missed it and didn't answer because I never read
it ...
Other things that bothered me,
 - niced processes are penalized
This can be considered a bug and should be fixed...
 - trying to kill a task that is permanently in TASK_UNINTERRUPTIBLE
   will probably deadlock the machine [or the random OOM killer will
   kill the box].
This could indeed be a problem, though I cannot really see any
case where a task would be in TASK_UNINTERRUPTIBLE permanently.
OTOH, a 1GB read() will take a (much) too long time to finish.

Your ideas sound really good, would you have the time to implement
them for 2.4 ?

regards,

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com.br/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help