linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Linux MM <linux-mm@kvack.org>,
	Linux Kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: [PATCH] swapin readahead and fixes
Date: Fri, 4 Dec 1998 15:02:56 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.3.96.981204150030.15134N-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199812041134.LAA01682@dax.scot.redhat.com>

On Fri, 4 Dec 1998, Stephen C. Tweedie wrote:
> On Thu, 3 Dec 1998 18:56:34 +0100 (CET), Rik van Riel
> <H.H.vanRiel@phys.uu.nl> said:
> 
> > The swapin enhancement consists of a simple swapin readahead.
> 
> One odd thing about the readahead: you don't start the readahead until
> _after_ you have synchronously read in the first swap page of the
> cluster.  Surely it is better to do the readahead first, so that you
> are submitting one IO to disk, not two?

This would severely suck when something else would be doing
a run_taskqueue(&tq_disk). It would mean that we'd read
n+1..n+15 before n itself.

OTOH, if the disk is lightly loaded it would be an advantage.
I will try it shortly (but don't know how to measure the
results :)...

cheers,

Rik -- the flu hits, the flu hits, the flu hits -- MORE
+-------------------------------------------------------------------+
| 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-12-04 14:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-03 17:56 Rik van Riel
1998-12-04 11:34 ` Stephen C. Tweedie
1998-12-04 14:02   ` Rik van Riel [this message]
1998-12-04 14:34     ` Stephen C. Tweedie
1998-12-05  9:46       ` Gerard Roudier
1998-12-07 16:50         ` Stephen C. Tweedie
1998-12-08  1:34           ` Billy Harvey
1998-12-08  2:31             ` Rik van Riel
1998-12-08  2:51               ` Billy Harvey
1998-12-08  3:00                 ` Rik van Riel
1998-12-08 12:35               ` Stephen C. Tweedie
1998-12-08 13:51                 ` Rik van Riel
1998-12-09  2:41               ` Drago Goricanec
1998-12-09 11:58                 ` Stephen C. Tweedie
1998-12-08 12:21             ` Stephen C. Tweedie
1998-12-05 10:47       ` Gerard Roudier
1998-12-04 19:25 ` Chris Evans
1998-12-04 20:47   ` Rik van Riel
1998-12-05 18:59     ` Alan Cox
1998-12-05 19:02       ` Rik van Riel
1998-12-06  5:20       ` Rik van Riel
1998-12-06  5:23       ` Steve VanDevender
1998-12-07 11:52   ` 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.981204150030.15134N-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@phys.uu.nl \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=sct@redhat.com \
    /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