From: Jonathan Morton <chromi@cyberspace.org>
To: Rik van Riel <riel@conectiva.com.br>, Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Marcelo Tosatti <marcelo@conectiva.com.br>,
Szabolcs Szakacsits <szaka@f-secure.com>
Subject: Re: [patch] swap-speedup-2.4.3-A1, massive swapping speedup
Date: Mon, 23 Apr 2001 17:53:18 +0100 [thread overview]
Message-ID: <l03130301b70a0e4c4676@[192.168.239.105]> (raw)
In-Reply-To: <Pine.LNX.4.21.0104231218000.1685-100000@imladris.rielhome.conectiva>
>There seems to be one more reason, take a look at the function
>read_swap_cache_async() in swap_state.c, around line 240:
>
> /*
> * Add it to the swap cache and read its contents.
> */
> lock_page(new_page);
> add_to_swap_cache(new_page, entry);
> rw_swap_page(READ, new_page, wait);
> return new_page;
>
>Here we add an "empty" page to the swap cache and use the
>page lock to protect people from reading this non-up-to-date
>page.
How about reversing the order of the calls - ie. add the page to the cache
only when it's been filled? That would fix the race.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-04-23 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 9:20 Ingo Molnar
2001-04-23 15:33 ` Rik van Riel
2001-04-23 16:05 ` [patch] swap-speedup-2.4.3-A2 Ingo Molnar
2001-04-23 17:17 ` Linus Torvalds
2001-04-23 16:54 ` Ingo Molnar
2001-04-24 5:44 ` [patch] swap-speedup-2.4.3-B3 Ingo Molnar
2001-04-24 16:38 ` Linus Torvalds
2001-04-25 2:28 ` Marcelo Tosatti
2001-04-23 16:53 ` Jonathan Morton [this message]
2001-04-23 17:10 ` [patch] swap-speedup-2.4.3-A1, massive swapping speedup Linus Torvalds
2001-04-23 22:13 ` Marcelo Tosatti
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='l03130301b70a0e4c4676@[192.168.239.105]' \
--to=chromi@cyberspace.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=mingo@elte.hu \
--cc=riel@conectiva.com.br \
--cc=szaka@f-secure.com \
--cc=torvalds@transmeta.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