From: Paul <set@pobox.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.10 much better than previous 2.4.x :-)
Date: Tue, 25 Sep 2001 20:35:15 -0400 [thread overview]
Message-ID: <20010925203515.A227@squish.home.loc> (raw)
In-Reply-To: <1001377785.1430.7.camel@gromit.house> <Pine.LNX.4.33L.0109242234410.19147-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0109242234410.19147-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Mon, Sep 24, 2001 at 10:35:53PM -0300
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 ?
>
> (The -ac VM has basically branched off at 2.4.7 and has
> evolved quite a bit since ... last week I fixed a stupid
> page aging bug and things should be a lot better than
> before now)
>
> regards,
>
> Rik
K6-333 128M ram
2.4.9-ac15 my impression: Well, running mutt with 80M
folder open, desktop with several aterms and netscape with a few
windows open, I started building a kernel in one term, and a
'find / -type f -exec md5sum {}' in another, then started reading
the mail, and occasionally jumping around the virtual desktop,
exposing netscapes... (this is pretty much my normal working
load, except for the find.)
I thought it worked very well; exposed netscapes were
either just there, or drew almost instantly. (other kernels I
have used, under the same load would usually take quite a bit
longer for exposed netscape to draw itself.) 'interactiveness'
seemed good.
Then, I read a post in this thread about swap being
funny. I noticed that no swap was being reported as used all
during my test. So, I forced the issue with an endless malloc.
Very quickly, the system seems to freeze, and the disk is
yammering away. I was waiting for the OOM killer to kick in,
but it never did. <alt><sysrq> works well, and I used it to print
out the Mem stats after several minutes. Eventually, I used
sysrq to sync and kill (couldnt get it to reBoot, though).
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?
Paul
set@pobox.com
SysRq : Show Memory
Mem-info:
Free pages: 1512kB ( 0kB HighMem)
( Active: 63, inactive_dirty: 172, inactive_clean: 0, free: 378 (351 702 1053) )
1*4kB 1*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB = 508kB)
25*4kB 3*8kB 1*16kB 1*32kB 1*64kB 0*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB = 1004kB)
= 0kB)
Swap cache: add 5, delete 5, find 0/0
Page cache size: 79
Buffer mem: 156
Ramdisk pages: 0
Free swap: 337148kB
32764 pages of RAM
0 pages of HIGHMEM
1038 reserved pages
115 pages shared
0 pages swap cached
0 pages in page table cache
Buffer memory: 624kB
next prev parent reply other threads:[~2001-09-26 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 0:29 Michael Rothwell
2001-09-25 1:35 ` Rik van Riel
2001-09-26 0:35 ` Paul [this message]
2001-09-26 20:08 ` José Luis Domingo López
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
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=20010925203515.A227@squish.home.loc \
--to=set@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®