From: Johannes Weiner <hannes@cmpxchg.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "Barnes, Jesse" <jesse.barnes@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Andi Kleen <andi@firstfloor.org>,
Minchan Kim <minchan.kim@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [patch v3] swap: virtual swap readahead
Date: Thu, 11 Jun 2009 12:17:42 +0200 [thread overview]
Message-ID: <20090611101741.GA1974@cmpxchg.org> (raw)
In-Reply-To: <20090611052228.GA20100@localhost>
On Thu, Jun 11, 2009 at 01:22:28PM +0800, Wu Fengguang wrote:
> Unfortunately, after fixing it up the swap readahead patch still performs slow
> (even worse this time):
Thanks for doing the tests. Do you know if the time difference comes
from IO or CPU time?
Because one reason I could think of is that the original code walks
the readaround window in two directions, starting from the target each
time but immediately stops when it encounters a hole where the new
code just skips holes but doesn't abort readaround and thus might
indeed read more slots.
I have an old patch flying around that changed the physical ra code to
use a bitmap that is able to represent holes. If the increased time
is waiting for IO, I would be interested if that patch has the same
negative impact.
Hannes
> before after
> 0.02 0.01 N xeyes
> 0.76 0.89 N firefox
> 1.88 2.21 N nautilus
> 3.17 3.41 N nautilus --browser
> 4.89 5.20 N gthumb
> 6.47 7.02 N gedit
> 8.16 8.90 N xpdf /usr/share/doc/shared-mime-info/shared-mime-info-spec.pdf
> 12.55 13.36 N xterm
> 14.57 15.57 N mlterm
> 17.06 18.11 N gnome-terminal
> 18.90 20.37 N urxvt
> 23.48 25.26 N gnome-system-monitor
> 26.52 27.84 N gnome-help
> 29.65 31.93 N gnome-dictionary
> 36.12 37.74 N /usr/games/sol
> 39.27 40.61 N /usr/games/gnometris
> 42.56 43.75 N /usr/games/gnect
> 47.03 47.85 N /usr/games/gtali
> 52.05 52.31 N /usr/games/iagno
> 55.42 55.61 N /usr/games/gnotravex
> 61.47 61.38 N /usr/games/mahjongg
> 67.11 65.07 N /usr/games/gnome-sudoku
> 75.15 70.36 N /usr/games/glines
> 79.70 74.96 N /usr/games/glchess
> 88.48 80.82 N /usr/games/gnomine
> 96.51 88.30 N /usr/games/gnotski
> 102.19 94.26 N /usr/games/gnibbles
> 114.93 102.02 N /usr/games/gnobots2
> 125.02 115.23 N /usr/games/blackjack
> 135.11 128.41 N /usr/games/same-gnome
> 154.50 153.05 N /usr/bin/gnome-window-properties
> 162.09 169.53 N /usr/bin/gnome-default-applications-properties
> 173.29 190.32 N /usr/bin/gnome-at-properties
> 188.21 212.70 N /usr/bin/gnome-typing-monitor
> 199.93 236.18 N /usr/bin/gnome-at-visual
> 206.95 261.88 N /usr/bin/gnome-sound-properties
> 224.49 304.66 N /usr/bin/gnome-at-mobility
> 234.11 336.73 N /usr/bin/gnome-keybinding-properties
> 248.59 374.03 N /usr/bin/gnome-about-me
> 276.27 433.86 N /usr/bin/gnome-display-properties
> 304.39 488.43 N /usr/bin/gnome-network-preferences
> 342.01 686.68 N /usr/bin/gnome-mouse-properties
> 388.58 769.21 N /usr/bin/gnome-appearance-properties
> 508.47 933.35 N /usr/bin/gnome-control-center
> 587.57 1193.27 N /usr/bin/gnome-keyboard-properties
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-11 10:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 19:01 Johannes Weiner
2009-06-09 19:37 ` Johannes Weiner
2009-06-10 5:03 ` Wu Fengguang
2009-06-10 7:45 ` Johannes Weiner
2009-06-10 8:11 ` Wu Fengguang
2009-06-10 8:32 ` KAMEZAWA Hiroyuki
2009-06-10 8:56 ` Wu Fengguang
2009-06-10 9:42 ` Peter Zijlstra
2009-06-10 9:59 ` Wu Fengguang
2009-06-10 10:05 ` Peter Zijlstra
2009-06-10 11:32 ` Wu Fengguang
2009-06-10 17:25 ` Jesse Barnes
2009-06-11 5:22 ` Wu Fengguang
2009-06-11 10:17 ` Johannes Weiner [this message]
2009-06-12 1:59 ` Wu Fengguang
2009-06-15 18:22 ` Johannes Weiner
2009-06-18 9:19 ` Wu Fengguang
2009-06-18 13:01 ` Johannes Weiner
2009-06-19 3:30 ` Wu Fengguang
2009-06-21 18:07 ` Hugh Dickins
2009-06-21 18:37 ` Johannes Weiner
2009-06-10 9:30 ` Johannes Weiner
2009-06-10 6:39 ` KAMEZAWA Hiroyuki
2009-06-11 5:31 ` KAMEZAWA Hiroyuki
2009-06-17 22:41 ` Johannes Weiner
2009-06-18 9:29 ` Wu Fengguang
2009-06-18 13:09 ` Johannes Weiner
2009-06-19 3:17 ` Wu Fengguang
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=20090611101741.GA1974@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=jesse.barnes@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=peterz@infradead.org \
--cc=riel@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