To: linux-kernel@vger.kernel.org
From: Oleg Verych <olecom@flower.upol.cz>
Subject: Re: strange behaviour with x86_64
Date: Thu, 16 Nov 2006 12:38:25 +0000 (UTC)
Organization: Palacky University in Olomouc, experimental physics department.
Message-ID: <slrnelonbf.7lr.olecom@flower.upol.cz>
References: <200611151608.23992.cova@ferrara.linux.it>
Mail-Followup-To: LKML <linux-kernel@vger.kernel.org>, Oleg Verych <olecom@flower.upol.cz>
User-Agent: slrn/0.9.8.1pl1 (Debian)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1180
Lines: 23

On 2006-11-15, Fabio Coatti wrote:
> Hi all,

I'm just trying to move things forward, i'm not a developer.

> I'm seeing a strange behaviour on a dual opteron machine (or, at least it seem 
> so to me) and I need some advice.
> The hardware is: dual opteron 2.4, dual core, 2GB ram
> This machine runs apache webserver/mod_perl. Due to some bug in perl code, 
> often the machine runs out of memory, and oomkiller triggers.

You seem to run very interesting distribution; when reporting
*kernel* bugs (things), try to follow REPORTING-BUGS (in top dir. of kernel
sources): version (ver_linux), adding to CC list memory management
list from MAINTAINERS file.

As for me, kernel in oom condition is very bad thing. I don't think
"oom killer" idea is working in general (while it helps to link
allyesconfig kernel on 1G without swap ;).

Thus, i suggest you to play with stuff, described in
"Documentation/vm/overcommit-accounting".
____

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