linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Chris Evans <chris@ferret.lmh.ox.ac.uk>
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] swapin readahead and fixes
Date: Mon, 7 Dec 1998 12:52:54 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.3.96.981207124716.23360D-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.96.981204192244.28834B-100000@ferret.lmh.ox.ac.uk>

On Fri, 4 Dec 1998, Chris Evans wrote:
> On Thu, 3 Dec 1998, Rik van Riel wrote:
> 
> > here is a patch (against 2.1.130, but vs. 2.1.131 should
> > be trivial) that improves the swapping performance both
> > during swapout and swapin and contains a few minor fixes.

Since Dec 3 a lot changed. There now _is_ a patch against the
2.1.131 with Stephen's apparantly excellent shrink_mmap() fix.

> I'm very interested in performance for sequential swapping. This
> occurs in for example scientific applications which much sweep
> through vast arrays much larger than physical RAM. 
> 
> Have you benchmarked booting with low physical RAM, lots of swap and
> writing a simple program that allocates 100's of Mb of memory and
> then sequentially accesses every page in a big loop? 

Yes. Zlatko Calusic made a small and simple program that you
can tell how much memory to use and how many passes it should
make. It simply reads the memory and dirties it. I have achieved
5 MB/s (that's 10 MB/s when you count the fact that you both have
to read _and_ write) on a 200 MB session.

> This is one area in which FreeBSD stomps on us. Theoretically it
> should be possible to get swap with readahead pulling pages into RAM
> at disk speed. 

I have looked at the FreeBSD code. We can do better than that
and I've worked out quite a nice scheme to do both read-ahead,
read-behind or a combination of the two (depending on the
situation). We also should stop reading in pages that are in
the vincinity but don't belong to the program at hand.

Unfortunately the Linux swapout code doesn't do proper clustering
yet (too much fragmentation within a program's address space) and
none of the above ideas have been converted to code yet. :)

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

      parent reply	other threads:[~1998-12-07 12:57 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
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 [this message]

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.981207124716.23360D-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@phys.uu.nl \
    --cc=chris@ferret.lmh.ox.ac.uk \
    --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