linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Gerard Roudier <groudier@club-internet.fr>
Cc: Peter-Paul Witta <e9525748@student.tuwien.ac.at>,
	Linux Kernel <linux-kernel@vger.rutgers.edu>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: increasing page size
Date: Mon, 6 Jul 1998 08:41:03 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.3.96.980706083755.3995B-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.95.980705212619.1514A-100000@localhost>

On Sun, 5 Jul 1998, Gerard Roudier wrote:
> On Sun, 5 Jul 1998, Rik van Riel wrote:
> 
> > Even if files are fragmented, readahead _will_ give a large
> > performance increase. This is because we can bring in the
> 
> This requires:
> 
> 1 - The program will really need the next page.
> 2 - The latency to get the next page is far lower than the program 
>     time execution before it will need of the next page.
> 3 - The page is still in memory when the program will 
>     need it.

With good algorithms, the kernel can make some quite proper
decisions on which readahead can be done and which readahead
is too expensive...

I believe Ingo's readahead code (not yet released) does something
like this. It analizes the programs' usage pattern and swaps in
until the page that has 50% probability of usage. If the program
soft-faults one of the preread pages, the kernel reads in the next
one(s) and this goes on until the kernel frees one of the preread
pages.

Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide.        H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader.      http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+

--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org

       reply	other threads:[~1998-07-06  9:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.95.980705212619.1514A-100000@localhost>
1998-07-06  6:41 ` Rik van Riel [this message]
     [not found] <19980705145314.A1909@uni-koblenz.de>
1998-07-05 18:04 ` Rik van Riel
     [not found] <Pine.A41.3.95.980705101710.48492B-100000@stud2.tuwien.ac.at>
1998-07-05 11:29 ` 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=Pine.LNX.3.96.980706083755.3995B-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@phys.uu.nl \
    --cc=e9525748@student.tuwien.ac.at \
    --cc=groudier@club-internet.fr \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.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