From: "Phil Oester" <kernel@theoesters.com>
To: "'Stephan von Krawczynski'" <skraw@ithnet.com>
Cc: <nknight@pocketinet.com>, <linux-kernel@vger.kernel.org>
Subject: RE: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
Date: Sun, 6 Jan 2002 22:22:16 -0800 [thread overview]
Message-ID: <000101c19743$a6dc4120$6400a8c0@philxp> (raw)
In-Reply-To: <20020105161727.18f04fc3.skraw@ithnet.com>
I've rerun this test a number of times, and cannot reliably reproduce
the OOM - though it still does OOM occasionally. It never OOM's right
after a bootup - usually the greatest chance of OOM is after 2 or 3
consecutive runs without a reboot. Once it even froze the box and
required a powercycle.
I'm surprised you cannot OOM with 1gb RAM/256MB swap, as sometimes I'm
over 900MB in swap - did you try consecutive runs, or just once and then
reboot between each run?
On a side note, there seems to be some debate as to whether this is a
valid test. The detractors primarily claim that 'make -j' just
overloads the machine with too many processes and therefore is setting
it up to fail. My position has always been that the kernel
_should_not_OOM_ under this test due to the ~2gb of ~RAM being thrown at
it. It may die for any number of other reasons, but OOM shouldn't be
one of them. In other words, either the OOM killer may be too
aggressive here, or the kernel isn't reclaiming inactive RAM under heavy
load.
Haven't yet tried Martin's patch - though since I can't reliably produce
the OOM, testing it wouldn't help much.
-Phil Oester
-----Original Message-----
From: Stephan von Krawczynski [mailto:skraw@ithnet.com]
Sent: Saturday, January 05, 2002 7:17 AM
To: Phil Oester
Cc: nknight@pocketinet.com; linux-kernel@vger.kernel.org
Subject: Re: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
I guess this testcase is somewhat driving in the direction of Martins
test with
some setis running, meaning it has a lot of standard processes that need
files
and try to work out something. Can you try Martins patch at your side,
redo the
-j story and give us a result? I attached it for an easy go :-)
Thanks,
Stephan
next prev parent reply other threads:[~2002-01-07 6:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:32 1gb RAM + 1gb SWAP + make -j bzImage = OOM Phil Oester
2002-01-04 21:02 ` Stephan von Krawczynski
2002-01-05 0:42 ` Nicholas Knight
2002-01-05 1:24 ` Phil Oester
2002-01-05 15:17 ` Stephan von Krawczynski
2002-01-07 6:22 ` Phil Oester [this message]
2002-01-07 14:24 ` Stephan von Krawczynski
2002-01-08 5:11 ` Phil Oester
2002-01-05 21:41 ` Eric W. Biederman
2002-01-05 12:30 ` Luigi Genoni
2002-01-05 15:19 ` Stephan von Krawczynski
2002-01-05 17:57 ` Nicholas Knight
2002-01-06 14:40 ` Stephan von Krawczynski
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='000101c19743$a6dc4120$6400a8c0@philxp' \
--to=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nknight@pocketinet.com \
--cc=skraw@ithnet.com \
/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