All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Thomas Schlichter <schlicht@rumms.uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: An idea for prefetching swapped memory...
Date: Mon, 07 Apr 2003 15:24:10 +0200	[thread overview]
Message-ID: <3E917BFA.4020303@aitel.hist.no> (raw)
In-Reply-To: 1049712476.3e91575c2e6ae@rumms.uni-mannheim.de

Thomas Schlichter wrote:

> What I wanted to say is that if there is free memory it should be filled with
> the pages that were in use before the memory got rare. And these are the pages
> swapped out last. 

Not necessarily.  Memory isn't merely used to hold swappable stuff, it also
caches files.  Consider a small but io-intensive program.  The stuff
you want isn't necessarily the last swap (perhaps there
even isn't anything swapped out) , it might be the last thing
dropped from cache instead.

And we can often predict better than "the last thing swapped/flushed"
A bunch of free memory appearing could usually be better used for
extra read-ahead, wether it is read-ahead of files/directories/bitmaps
being accessed, or executable code faulted in from executables or
swap devices.

> The other swapped out pages are swapped out even longer and so
> will likely not be used in the near future... (That's what the LRU algorithm
> says...)


"What we're going to need soon" is the best.  It isn't always predictable,
but sometimes.  "The block following the last we read from some 
file/fs-structure"
is often a good one though.

Helge Hafting


  parent reply	other threads:[~2003-04-07 13:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07  8:26 An idea for prefetching swapped memory Thomas Schlichter
2003-04-07 10:21 ` Con Kolivas
2003-04-07 10:47   ` Thomas Schlichter
2003-04-07 11:24     ` Måns Rullgård
2003-04-07 12:46       ` Thomas Schlichter
2003-04-07 18:33       ` Mark Mielke
2003-04-07 13:24     ` Helge Hafting [this message]
2003-04-07 14:19       ` Chris Friesen
2003-04-07 14:39         ` Jörn Engel
2003-04-07 18:37         ` Mark Mielke
2003-04-07 18:49           ` Chris Friesen
2003-04-07 19:35             ` Mark Mielke
2003-04-07 19:39             ` Robert White
2003-04-07 20:44               ` Chris Friesen
2003-04-07 11:36   ` Christophe Saout
2003-04-07 11:48     ` Måns Rullgård
2003-04-07 12:19       ` Jörn Engel
2003-04-07 12:45         ` Christophe Saout
2003-04-07 16:30   ` Magnus Danielson
2003-04-07 12:32 ` David Zaffiro
2003-04-07 12:43   ` Jörn Engel

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=3E917BFA.4020303@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schlicht@rumms.uni-mannheim.de \
    /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.