From: Rik van Riel <riel@conectiva.com.br>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org, Arjan van de Ven <arjanv@redhat.com>
Subject: [PATCH][RFC] split active lists for rmap 15
Date: Thu, 21 Nov 2002 22:12:03 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.44L.0211212208070.4103-100000@imladris.surriel.com> (raw)
Hi,
it turns out that while Arjan's O(1) VM code works fine in
most scenarios, it's too swap happy in some cases. In order
to try to fix that I've split up the (per zone) active list
into an active_anon list (process working set) and an
active_cache list (file cache).
If the active_cache list is "large" we deactivate those pages
preferentially. Of course, if those pages really are referenced
they'll just be moved back to the active list and we'll end up
swapping out processes ... but in the common case of streaming
over lots and lots of file data we'll swap out the processes
very slowly, meaning that the machine should stay nicely usable
during eg. bitkeeper pulls, backups and apt-get updates.
This patch is still experimental, so any testing is welcome.
As usual, you can grab it from http://surriel.com/patches/
http://surriel.com/patches/2.4/2.4.19-rmap15-splitactive
have fun,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://guru.conectiva.com/
Current spamtrap: <a href=mailto:"october@surriel.com">october@surriel.com</a>
--
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-mm.org/
reply other threads:[~2002-11-22 0:12 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.4.44L.0211212208070.4103-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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