From: William Lee Irwin III <wli@holomorphy.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
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 09:28:20 -0700 [thread overview]
Message-ID: <20041012162820.GY9106@holomorphy.com> (raw)
In-Reply-To: <416BF72F.2080804@nortelnetworks.com>
>On Mon, Oct 11, 2004 at 11:03:16PM -0600, 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?
William Lee Irwin III wrote:
>> Not so. Just add enough swapspace to act as the backing store for the
>> aggregate anonymous virtualspace.
On Tue, Oct 12, 2004 at 09:24:31AM -0600, Chris Friesen wrote:
> In my first message I mentioned that I had no swap. It's embedded, so I do
> not have the ability to add swap.
Then the closest thing to a good idea may be to enable overcommitment.
echo 1 > /proc/sys/vm/overcommit_memory to do that.
-- wli
next prev parent reply other threads:[~2004-10-12 16:28 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 [this message]
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
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=20041012162820.GY9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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