From: "José Luis Domingo López" <jdomingo@internautas.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Paul <set@pobox.com>, Rik van Riel <riel@conectiva.com.br>
Subject: Re: 2.4.10 much better than previous 2.4.x :-)
Date: Wed, 26 Sep 2001 20:08:33 +0000 [thread overview]
Message-ID: <20010926200833.A1859@dardhal.mired.net> (raw)
In-Reply-To: <1001377785.1430.7.camel@gromit.house> <Pine.LNX.4.33L.0109242234410.19147-100000@imladris.rielhome.conectiva> <20010925203515.A227@squish.home.loc>
In-Reply-To: <20010925203515.A227@squish.home.loc>
On Tuesday, 25 September 2001, at 20:35:15 -0400,
Paul wrote:
> Rik van Riel <riel@conectiva.com.br>, on Mon Sep 24, 2001 [10:35:53 PM] said:
> >
> > If you have the time, could you also test 2.4.9-ac15 ?
> > [...]
> Im not complaining-- Im just curious why no OOM killing,
> and the Mem stats report 337148k swap free (I have 337168k).
> Does this memmory report look proper for a machine thrashing
> itself to death from endless mallocs?
>
I've done several test with various versions of 2.4.x kernels, just to
make sure OOM worked right or not. I've used setups with both swap and no
swap, with swap double the RAM and equal to it, from a single user mode
and full multiuser with tons of applications running.
To reach OOM I try one of two methods: first, the well-know glob() DoS
(ls ../*/../*/../*/ etc), second, starting as many applications as I can,
loading and creating huge images with gimp, etc.
In my test, OOM seems to work well most of the time, but not always. When
in works, it works fine, that is, it doesn't kill applications too early,
and (in recent kernel), multithreaded applications (like mozilla and
staroffice) and fully wiped from memory ("old" 2.4.x kernels didn't kill
all the threads, just the selected process ID).
When OOM doesn't work, the disk starts spinning like crazy, responsiveness
in null, mouse doesn't move, consoles don't update, unability to switch to
text consoles, etc. Giving time to the machine to recover itself is not
helpful: after more than 15 minutes the disk continue to spin and sound
like they were to inmediately crash :)
But in this situation, SysRq+K work fine most of the times: in a couple of
seconds the disk stops its crazyness, and the machine recovers. The text
console is unusable (can't display a thing), but issuing a "startx"
blindly works as expected, as if nothing had happened.
I've tried playing with "freepages" tunnable (where it exists), to raise
limits and (hopefully) keep more RAM free for the kernel for the hard
times where it tries to recover from OOM. OOM still fails sometimes, but
maybe I don't understand what freepages.[min|low|high] mean (having read
documentation under linux/Documentation :)
--
José Luis Domingo López
Linux Registered User #189436 Debian Linux Woody (P166 64 MB RAM)
jdomingo EN internautas PUNTO org => ¿ Spam ? Atente a las consecuencias
jdomingo AT internautas DOT org => Spam at your own risk
next prev parent reply other threads:[~2001-09-26 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 0:29 2.4.10 much better than previous 2.4.x :-) Michael Rothwell
2001-09-25 1:35 ` Rik van Riel
2001-09-26 0:35 ` Paul
2001-09-26 20:08 ` José Luis Domingo López [this message]
2001-09-27 8:17 ` Helge Hafting
2001-09-28 4:53 ` Paul
2001-09-25 15:20 ` Something Broken in 2.4.9-ac15 Kent Borg
2001-09-25 16:51 ` Kent Borg
2001-09-26 0:06 ` 2.4.10 much better than previous 2.4.x :-) Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 16:18 Martin Knoblauch
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=20010926200833.A1859@dardhal.mired.net \
--to=jdomingo@internautas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=set@pobox.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