From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: strange behaviour with x86_64
Date: Thu, 16 Nov 2006 12:38:25 +0000 (UTC) [thread overview]
Message-ID: <slrnelonbf.7lr.olecom@flower.upol.cz> (raw)
In-Reply-To: <200611151608.23992.cova@ferrara.linux.it>
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".
____
prev parent reply other threads:[~2006-11-16 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 15:08 Fabio Coatti
2006-11-16 12:38 ` Oleg Verych [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnelonbf.7lr.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®