From: MrChuoi <MrChuoi@yahoo.com>
To: Mike Fedyk <mfedyk@matchmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-pre3-ac1
Date: Mon, 18 Mar 2002 10:02:33 +0700 [thread overview]
Message-ID: <20020318025233.A7C044E534@mail.vnsecurity.net> (raw)
In-Reply-To: <20020316190415.38CE14E534@mail.vnsecurity.net> <E16mLFj-000794-00@the-village.bc.nu> <20020317053624.GD23938@matchmail.com>
In-Reply-To: <20020317053624.GD23938@matchmail.com>
On Sunday 17 March 2002 12:36 pm, Mike Fedyk wrote:
> > So you have 128Mb of RAM, 64Mb of swap, and if all pages are touched you
> > would need 226Mb of swap + ram (minus kernel overhead). Looks like the
> > machine is hovering on the edge
>
> In Other Words (IOW), add more swap like everyone else said.
>
> The rmap design does use a bit more memory (about 400k for 128MB ram) for
> the reverse mapping tables, so that could push you over into an OOM case.
It seems that OOM killer doesn't work in 2.4.19-pre2-ac4 and 2.4.19-pre3-ac1.
I try to load alot of apps (KDE apps + JBuilder) as much as possible until
swap free = 0. At this time, if I try to load a big enough app (KDE Media in
my case), kernel should start OOM killer. But 2.4.19-pre-ac didn't, it try to
.... swap ;), kswapd runs like crazy (30%-40%CPU), disk access continuously,
and whole system is un-interractive => push restart button after 1 hour
waiting for OOM kill.
Behavior of some kernels in this case:
- 2.4.19-pre3: Start OOM killer to kill SOME java processes (JBuilder) before
KDE Media starts and continue to kill all re-spawned java processes. System
is slow down but still interactivable and back to normal status if close some
apps.
- 2.4.19-pre-aa: Start OOM killer to kill ALL java processes (JBuilder) or
kill KDE Media immediately. System is still interactivable.
- 2.4.19-pre-ac: kswapd try to swap out and access disk continuously. Whole
system is slow down and un-interactivable.
HTH,
MrChuoi
next prev parent reply other threads:[~2002-03-18 2:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 1:42 Linux 2.4.19-pre3-ac1 Alan Cox
2002-03-16 2:44 ` Mike Fedyk
2002-03-16 5:33 ` MrChuoi
2002-03-16 6:00 ` J Sloan
2002-03-16 7:52 ` MrChuoi
2002-03-16 17:30 ` Alan Cox
2002-03-16 17:50 ` MrChuoi
2002-03-16 18:00 ` Alan Cox
2002-03-16 19:14 ` MrChuoi
2002-03-16 20:58 ` Alan Cox
2002-03-17 5:36 ` Mike Fedyk
2002-03-17 23:52 ` Matthew D. Pitts
2002-03-18 0:01 ` Mike Fedyk
2002-03-18 3:02 ` MrChuoi [this message]
2002-03-18 3:01 ` Mike Fedyk
2002-03-18 3:03 ` Rik van Riel
2002-03-19 1:46 ` MrChuoi
2002-03-18 11:44 ` Alan Cox
2002-03-18 21:23 ` toon
2002-03-19 1:39 ` MrChuoi
2002-03-19 1:55 ` Alan Cox
2002-03-19 5:54 ` Zwane Mwaikambo
2002-03-19 6:20 ` Mike Fedyk
2002-03-19 6:46 ` Zwane Mwaikambo
2002-03-19 13:32 ` Alan Cox
2002-03-19 18:04 ` Mike Fedyk
2002-03-19 18:26 ` Alan Cox
2002-03-19 18:29 ` Mike Fedyk
2002-03-21 5:11 ` Mike Fedyk
2002-03-21 13:32 ` Alan Cox
2002-03-18 5:24 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2002-03-17 13:55 jarmo kettunen
2002-03-17 17:23 ` Alan Cox
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=20020318025233.A7C044E534@mail.vnsecurity.net \
--to=mrchuoi@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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