From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: Bill Hawes <whawes@star.net>,
Linux Kernel List <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org
Subject: Re: patch for 2.1.102 swap code
Date: Tue, 26 May 1998 23:46:35 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.91.980526234356.11319A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199805262138.WAA02811@dax.dcs.ed.ac.uk>
On Tue, 26 May 1998, Stephen C. Tweedie wrote:
> That's why read_swap_cache_async repeats the initial entry lookup after
> calling __get_free_page(). Unfortunately, I hadn't realised that
> swap_duplicate() had the error check against swap_map[entry]==0. Moving
> the swap_duplicate up to before the call to __get_free_page should avoid
> that case.
Hmm, could read_swap_cache_async() be used to implement swap
readahead?
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.phys.uu.nl/~riel/ | <H.H.vanRiel@phys.uu.nl> |
+-------------------------------------------+--------------------------+
next prev parent reply other threads:[~1998-05-26 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <356478F0.FE1C378F@star.net>
1998-05-24 17:28 ` Stephen C. Tweedie
1998-05-25 10:07 ` David S. Miller
1998-05-25 12:38 ` Eric W. Biederman
1998-05-26 21:52 ` Stephen C. Tweedie
1998-06-11 14:31 ` Eric W. Biederman
1998-06-12 21:29 ` Stephen C. Tweedie
1998-05-25 12:52 ` Bill Hawes
1998-05-25 13:42 ` David S. Miller
1998-05-26 18:00 ` Stephen C. Tweedie
1998-05-26 21:38 ` Stephen C. Tweedie
1998-05-26 21:46 ` Rik van Riel [this message]
1998-06-02 22:21 ` Stephen C. Tweedie
1998-05-27 15:27 ` Bill Hawes
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.91.980526234356.11319A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
--cc=whawes@star.net \
/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