All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@cs.columbia.edu>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Shaya Potter <spotter@opus.cs.columbia.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: replacing the page replacement algo.
Date: 18 Nov 2001 21:31:15 -0500	[thread overview]
Message-ID: <1006137133.604.8.camel@zaphod> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111182344150.4079-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0111182344150.4079-100000@imladris.surriel.com>

On Sun, 2001-11-18 at 20:44, Rik van Riel wrote:
> On 18 Nov 2001, Shaya Potter wrote:
> 
> > If I wanted to experiment with different algorithms that chose which
> > page to replace (say on a page fault) what functions would I have to
> > replace?
> 
> try_to_free_pages() and all the functions it calls.

I was looking at vmscan.c and it appears that swap_out() is what I
want.  If instead of having it step through the mmlist, I give it the
explicit mm of the processes that I want a page swapped out from? so I
could implement my algorithm either inside that func or as function
calls from it and have it pass onto swap_out_mm() the mm of the
processes I choose to swap out.

or am I totally misunderstanding something here? (likely, as this is my
first time digging into the vm and trying to learn about it)

thanks,

shaya potter


  reply	other threads:[~2001-11-19  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19  0:17 replacing the page replacement algo Shaya Potter
2001-11-19  1:44 ` Rik van Riel
2001-11-19  2:31   ` Shaya Potter [this message]
2001-11-19  2:38     ` Rik van Riel
2001-11-19  2:51       ` Shaya Potter
2001-11-20  3:49         ` Eric W. Biederman
2001-12-28  8:23         ` Daniel Phillips
2001-12-28 12:22           ` Rik van Riel

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=1006137133.604.8.camel@zaphod \
    --to=spotter@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=spotter@opus.cs.columbia.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.