From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: linux-mm <linux-mm@kvack.org>
Cc: linux-kernel <linux-kernel@vger.rutgers.edu>
Subject: vhand design flaw :((, new patch instead
Date: Tue, 9 Dec 1997 18:43:13 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971209183412.8252A@mirkwood.dummy.home> (raw)
Hi,
I found (much to my dissapointment) a fundamental design flaw
in my vhand patch that explains very well the different results
people have had with my patch. It doesn't affect stability,
just performance, so when vhand works for you, there's no
reason not to use it anymore, except for the fact that something
better's around...
The new patch consists of two parts:
- the anti-fragmentation patch from Zlatko Calusic (really useful)
- kswapd now also ages mmap'ed pages. for this part I have just
copied some code from vmscan.c into mmap.c, so it should all
be rock-solid...
The results of this patch are:
- kswapd is more careful about kicking out mmap'ed pages and
buffers and as a result of this:
- kswapd takes more CPU time to swap out a page
- kswapd has to swap out less pages
- there are (far) less pagefaults
- now there's no vhand daemon that constantly uses CPU
I hope that the total CPU usage of kswapd hasn't increased
much, if it has increased at all. I for one know that system
performance was boosted quite a bit (more than with the vhand
patch).
If this runs for a lot of people, I'll even send it to Linus
(there's no new code in it, so we can consider this a bug-fix)
grtz,
Rik.
ps: making it a config option is also possible... We could
even consider adding another (simpler) aging algorithm to
kswapd for (huge) systems that have more I/O bandwith to spare
than they have CPU time.
--
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...
reply other threads:[~1997-12-09 17:55 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=Pine.LNX.3.91.971209183412.8252A@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
/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