From: Chris Ross <chris@tebibyte.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: slow OOM killing with 2.6.9?
Date: Thu, 16 Dec 2004 12:54:34 +0100 [thread overview]
Message-ID: <41C1777A.3080105@tebibyte.org> (raw)
In-Reply-To: <41C065A2.4040504@nortelnetworks.com>
Chris Friesen escreveu:
> I've got a ppc box with 2GB of ram, running 2.6.9.
>
> If I run a few instances of memory chewing programs, eventually the
> OOM-killer kicks in. At that point, the machine locks up for about 10
> seconds while deciding what to kill.
OOM killing is known to be broken in 2.6.9, specifically it kills things
even when the machine isn't out of memeory and/or kills the "wrong"
things when it is. See threads assim for more details.
The OOM Killer is working properly again in 2.6.10-rc2-mm4. Could you
try that kernel and report whether it fixed your problems too?
Regards,
Chris R.
next prev parent reply other threads:[~2004-12-16 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 16:26 slow OOM killing with 2.6.9? Chris Friesen
2004-12-16 11:54 ` Chris Ross [this message]
2004-12-16 16:36 ` Chris Friesen
2004-12-16 17:10 ` Chris Friesen
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=41C1777A.3080105@tebibyte.org \
--to=chris@tebibyte.org \
--cc=cfriesen@nortelnetworks.com \
--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