From: Shaya Potter <spotter@cs.columbia.edu>
To: linux-kernel@vger.kernel.org
Subject: replacing the page replacement algo.
Date: 18 Nov 2001 19:17:11 -0500 [thread overview]
Message-ID: <1006129088.605.2.camel@zaphod> (raw)
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? or in other words, is there any good place that explains the
code path of how pages are chosen to be swapped out. For example, by
scheduling, its easy to replace the scheduler because all you need to
deal with is schedule() and possibly add_to/del_from runqueue, with
schedule() being the important function, is there an equivalent function
in 2.4 for choosing pages to swap out?
thanks,
shaya potter
--
spotter@{cs.columbia.edu,yucs.org}
next reply other threads:[~2001-11-19 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 0:17 Shaya Potter [this message]
2001-11-19 1:44 ` replacing the page replacement algo 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
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=1006129088.605.2.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.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