[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070722023923.GA6438@mail.ustc.edu.cn>
Date: Sun, 22 Jul 2007 10:39:23 +0800
From: Fengguang Wu <wfg@...l.ustc.edu.cn>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
riel <riel@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Rusty Russell <rusty@...tcorp.com.au>,
Tim Pepper <lnxninja@...ibm.com>,
Chris Snook <csnook@...hat.com>, Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 0/3] readahead drop behind and size adjustment
On Sat, Jul 21, 2007 at 11:00:05PM +0200, Peter Zijlstra wrote:
> The various readahead bits I have lying about.
>
> Wu, would you agree with asking Andrew to stick these behind your latest
> readahead series?
They are generally good feature to have. Thank you!
- default readahead size
It makes sense to raise it beyond 128K. 1M default readahead
absolutely makes sense for sequential workloads. For the desktop,
this increases boot speed and readahead misses, both due to more
aggressive mmap read-around. Most users will be glad to feel the
speedup, and happily ignore the readahead misses, which may be
"invisible" in case of large memory.
In theory, the distributions can do the same tuning. So we have an
interesting question for Dave:
Does fedora desktop raise the default readahead size? Why or
why not? It goes so far to do userland readahead ;)
- drop behind
Sorry, I still doubt it will benefit all/most workloads. Leave it off
by default, and leave the enabling decision to Dave? I do hope that
it help general desktops.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists