Message-ID: <466FB6E8.8020606@free.fr>
Date: Wed, 13 Jun 2007 11:20:40 +0200
From: John Sigler <linux.kernel@free.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061108 SeaMonkey/1.0.6
MIME-Version: 1.0
To: Andrea Arcangeli <andrea@suse.de>
CC: linux-kernel@vger.kernel.org
Subject: Re: Runaway process and oom-killer
References: <466FAF99.3070708@free.fr> <20070613090837.GD7443@v2.random>
In-Reply-To: <20070613090837.GD7443@v2.random>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1238
Lines: 31

Andrea Arcangeli wrote:

> On Wed, Jun 13, 2007 at 10:49:29AM +0200, John Sigler wrote:
>
>> Question 2: how can I tell which process or kernel thread was hogging 
>> most of the RAM when the oom-killer kicked in?
> 
> Theoretically the one that was killed first but not for sure in
> current mainline hence see below.

If I read the logs correctly, oom-killer is "invoked" three times before 
it effectively kills a process. Then oom-killer kills myapp, syslogd, 
and boa, in that order. Why didn't oom-killer kill anything the first 
three times?

>> Question 3: if myapp was hogging the RAM, then why did oom-killer snipe 
>> other processes (syslogd and boa) after it killed myapp?
> 
> Please try again after applying this monolith (proper submission was
> on linux-mm but the monolith is easier to apply for tests like this):
> 
>    http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.22-rc4/oom-fixes-1

Would this patch apply to a 2.6.20.7-rt8 source tree?

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