From: Ryan Cumming <bodnar42@phalynx.dhs.org>
To: vda <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM killer in 2.4.15pre1 still not 100% ok
Date: Thu, 22 Nov 2001 08:15:18 -0800 [thread overview]
Message-ID: <E166wVS-0004Vk-00@localhost> (raw)
In-Reply-To: <01112217224700.01298@manta>
In-Reply-To: <01112217224700.01298@manta>
On November 22, 2001 11:22, vda wrote:
> Today I saw OOM killer in action for the very fist time.
> Just want to inform that it still not 100% ok (IMHO):
>
> I reconfigured my text box for NFS root fs operation
> and turned off swap. The box has 128M RAM.
...
> 5:01pm up 1:08, 3 users, load average: 0.18, 0.10, 0.06
> 61 processes: 58 sleeping, 2 running, 1 zombie, 0 stopped
> CPU states: 1.9% user, 15.6% system, 0.0% nice, 82.3% idle
> Mem: 126272K av, 123428K used, 2844K free, 0K shrd, 16K buff
>Swap: 0K av, 0K used, 0K free 47748K cached
Er, with almost 3megs of free memory and -47megs- of cache, the problem isn't
with the OOM killer's selection, but the fact it was triggered with nearly
half the RAM still usable. Do you actually know the OOM killer was triggered?
Or did top just mysteriously exit?
Personally, I've found the new 2.4.14+ OOM killer to be highly accurate, I've
run ext3's shared mappings torture test on my 384meg RAM (256meg swap) box
repeatedly, and it pushes my computer to OOM every 60 seconds or so. It
always kills the correct process, with my box remaining absolutely stable,
even with less swap space than RAM.
-Ryan
next prev parent reply other threads:[~2001-11-22 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 19:22 OOM killer in 2.4.15pre1 still not 100% ok vda
2001-11-22 16:15 ` Ryan Cumming [this message]
2001-11-22 21:42 ` vda
2001-11-23 15:00 ` vda
2001-11-26 10:24 ` Helge Hafting
2001-11-22 20:10 ` Mike Galbraith
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=E166wVS-0004Vk-00@localhost \
--to=bodnar42@phalynx.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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