From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] swapin readahead
Date: Thu, 3 Dec 1998 15:44:07 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.3.96.981203153155.216A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199812021733.RAA04470@dax.scot.redhat.com>
On Wed, 2 Dec 1998, Stephen C. Tweedie wrote:
> On 01 Dec 1998 18:20:49 +0100, Zlatko Calusic <Zlatko.Calusic@CARNet.hr>
> said:
>
> > Yes. something like that. Since nobody asked pages to swap in (we
> > decided to swap them in) it looks like nobody frees them. :)
> > So we should free them somewhere, probably.
>
> I think read_swap_page_async should be acting as a lookup on the page
> cache, so the page it returns is guaranteed to have an incremented
> reference count. You'll need to free_page() it just after the
> read_swap_page_async() call to get the expected behaviour.
I have now included the free_page() and things seem to work
out fine. In version 6 of the swapin readahead patch I also
fixed the swap_cache_find_* statistics. We really should make
those available through /proc/sys/vm/swapcache (and writable
so we can test the stats over a certain period of time).
Zlatko's hogmem.c gives pretty decent performance now, but I
guess it could be better by always doing readahead regardless
of whether the page is in memory or not...
OTOH, I have observed swapin rates of 5000+ swaps a second, or
3000 in/out :)
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
prev parent reply other threads:[~1998-12-03 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-26 23:23 Rik van Riel
1998-12-01 15:13 ` Stephen C. Tweedie
1998-12-01 15:41 ` Rik van Riel
1998-12-01 15:51 ` Zlatko Calusic
1998-12-01 16:42 ` Rik van Riel
1998-12-01 17:20 ` Zlatko Calusic
1998-12-01 18:32 ` Rik van Riel
1998-12-02 17:35 ` Stephen C. Tweedie
1998-12-02 21:18 ` Zlatko Calusic
1998-12-03 5:25 ` Eric W. Biederman
1998-12-03 8:55 ` Zlatko Calusic
1998-12-03 15:39 ` Eric W. Biederman
1998-12-03 10:07 ` Rik van Riel
1998-12-02 17:33 ` Stephen C. Tweedie
1998-12-03 14:44 ` 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.981203153155.216A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=Zlatko.Calusic@CARNet.hr \
--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