From: Cesar Eduardo Barros <cesarb@nitnet.com.br>
To: "Juan J. Quintela" <quintela@fi.udc.es>
Cc: linux-mm@kvack.org
Subject: linux-2.4.0-test1-ac22-riel+quintela
Date: Tue, 20 Jun 2000 23:13:46 -0300 [thread overview]
Message-ID: <20000620231346.A9382@cesarb.personal> (raw)
Finished the testing here on leaf (the 386).
dpkg --list caused kswapd get at 25% CPU max (an spike while doing the final
printing) and 12% on average (and also max before it started printing).
It was fast enough to be usable (not as fast as ac19 with that test deleted,
but if it's faster on other boxen I can stand it =) ).
vmstat 1 updates sometimes got delayed by about 2-3 secs (comparing with vmstat
in the other (unloaded) box). Hacked ac19 didn't have these delays.
Free memory normal (unlike hacked ac19 which had a bit more free mem).
The test was with ac22-riel and both quintela's patches for ac22-riel, plus my
own nvramfix5 patch (harmless since it's in a module).
So ac19 without the zone tests in shrink_mmap still win. I wonder why.
--
Cesar Eduardo Barros
cesarb@nitnet.com.br
cesarb@dcc.ufrj.br
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
reply other threads:[~2000-06-21 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000620231346.A9382@cesarb.personal \
--to=cesarb@nitnet.com.br \
--cc=linux-mm@kvack.org \
--cc=quintela@fi.udc.es \
/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