Message-ID: <496C73DE.3030600@wpkg.org>
Date: Tue, 13 Jan 2009 11:58:38 +0100
From: Tomasz Chmielewski <mangoo@wpkg.org>
User-Agent: Thunderbird 2.0.0.18 (X11/20081120)
MIME-Version: 1.0
To: LKML <linux-kernel@vger.kernel.org>, zbr@ioremap.net
Subject: Re: Linux killed Kenny, bastard!
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1386
Lines: 37

>> On Tue, 13 Jan 2009, Evgeniy Polyakov wrote:
>> 
>> > Like anything that spawns a thread or process per request/client, or
>> > preallocates set of them which connect to the huge object like database.
>> > Most of the time database/server is killed first instead of comparably
>> > small clients.
>> 
>> No, the reverse is true: when a task is chosen for oom kill based on the 
>> badness heuristic, the oom killer first attempts to kill any child task 
>> that isn't attached to the same mm.  If the child shares an mm, both tasks 
>> must die before memory freeing can occur.
> 
> It is a theory, not a practice. OOM-killer most of time starts from ssh,
> database and lighttpd on the tested machines, when it could start in
> the reverse order and do not touch ssh at all. Better not from daemon
> itself, but its fastcgi spawned processes.

How does this feature relate to:

config ANDROID_LOW_MEMORY_KILLER
         bool "Android Low Memory Killer"
         default N
         ---help---
           Register processes to be killed when memory is low

available in Staging drivers / Android?


-- 
Tomasz Chmielewski
http://wpkg.org

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