From: Shaya Potter <spotter@cs.columbia.edu>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: replacing the page replacement algo.
Date: 18 Nov 2001 21:51:44 -0500 [thread overview]
Message-ID: <1006138361.605.12.camel@zaphod> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111190037550.4079-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0111190037550.4079-100000@imladris.surriel.com>
On Sun, 2001-11-18 at 21:38, Rik van Riel wrote:
> On 18 Nov 2001, Shaya Potter wrote:
> > 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.
>
> You're missing the fact here that swap_out() only unmaps
> pages from processes' page tables, actual reclaiming of
> the pages is done elsewhere.
ok, but if what I'm interested in playing with right now is playing
around with which pages get swapped out, and not with the actual
reclamation procedure, is it ok to just play with swap_out and having it
do the thing it does, and let the rest of the kernel behave as is, or
will this cause problems?
thanks again,
shaya potter
next prev parent reply other threads:[~2001-11-19 2:53 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
2001-11-19 2:38 ` Rik van Riel
2001-11-19 2:51 ` Shaya Potter [this message]
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=1006138361.605.12.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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