linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.rutgers.edu
Subject: [bagpatch] VM sneak preview
Date: Fri, 26 May 2000 22:25:26 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0005262219400.16128-100000@duckman.distro.conectiva> (raw)

Hi,

as Roger Larson pointed out, one detail from my "new VM
sneak preview" patch doesn't make much sense. It does
not affect stability <hint> the patch has been running
smoothly for a number of people, you may want to try it</hint>.

You can fix it by editing mm/filemap.c and changing the
following code fragment (around line 270):

+               if (PageTestandClearReferenced(page)) {
+                       page->age += 3;
+                       if (page->age > 10)
+                               page->age = 0;
                                           ^^ should be 10
+                       goto dispose_continue;
+               }

Here the code checks if page->age exceeds the maximum. Of
course page->age should be set to the maximum value if it
does, and not all the way down to 0 :)

If you checked the patch and wondered why performance wasn't
always good ... this is it, things should just work now...

regards,

Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.

Wanna talk about the kernel?  irc.openprojects.net / #kernelnewbies
http://www.conectiva.com/		http://www.surriel.com/

--
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-05-27  1:25 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.21.0005262219400.16128-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --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