public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: replacing the page replacement algo.
Date: 19 Nov 2001 20:49:06 -0700	[thread overview]
Message-ID: <m14rnq6r0t.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111190037550.4079-100000@imladris.surriel.com> <1006138361.605.12.camel@zaphod>
In-Reply-To: <1006138361.605.12.camel@zaphod>

Shaya Potter <spotter@cs.columbia.edu> writes:

> 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?

The name of swap_out is historical.  It currently does no writing to
disk it just removes the page from the page tables.  But the page is
still in RAM.  The other routines are what decide which page should
actually be reused, or which pages get written.

The current code is both simple, auto-tuning and does a fairly good
job so look very closely at it before trying to randomly tune it. 

Eric

  reply	other threads:[~2001-11-20  4:08 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
2001-11-20  3:49         ` Eric W. Biederman [this message]
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=m14rnq6r0t.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=spotter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox