From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] oom killer not triggering in 2.6.9-rc3
Date: Tue, 12 Oct 2004 16:25:19 -0600 [thread overview]
Message-ID: <416C59CF.1020700@nortelnetworks.com> (raw)
In-Reply-To: <1097614971.2639.1.camel@localhost.localdomain>
Alan Cox wrote:
> On Maw, 2004-10-12 at 06:03, Chris Friesen wrote:
>>I must be able to run an app that uses over 90% of system memory, and calls
>>fork(). I was under the impression this made strict accounting unfeasable?
> Its rather smarter than that, you'll want swap probably. The strict
> accountant is a virtual address accountant not a memory accountant. It
> knows shared r/o segments don't need charging all the time etc
As I said in the first message, I've got no swap.
In any case, moving to -rc4 seems to have cleared up the issue, the patch Chris
Wright suggested seems to have worked. Oom killer now wakes up immediately and
kills one of the memory hogs, and the system continues on.
Chris
prev parent reply other threads:[~2004-10-12 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 0:14 [BUG] oom killer not triggering in 2.6.9-rc3 Chris Friesen
2004-10-09 0:26 ` Chris Wright
2004-10-11 13:58 ` Alan Cox
2004-10-12 5:03 ` Chris Friesen
2004-10-12 5:22 ` William Lee Irwin III
2004-10-12 15:24 ` Chris Friesen
2004-10-12 16:28 ` William Lee Irwin III
2004-10-12 9:44 ` Andries Brouwer
2004-10-12 15:32 ` Chris Friesen
2004-10-12 20:08 ` Chris Wright
2004-10-12 20:41 ` [BUG] oom killer not triggering in 2.6.9-rc3 -- FIXED in -rc4 Chris Friesen
2004-10-12 20:54 ` Chris Wright
2004-10-12 21:02 ` [BUG] oom killer not triggering in 2.6.9-rc3 Alan Cox
2004-10-12 22:25 ` Chris Friesen [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=416C59CF.1020700@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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