From: Andi Kleen <andi@firstfloor.org>
To: Fengguang Wu <fengguang.wu@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Oleg Nesterov <oleg@tv-sign.ru>,
Steven Pratt <slpratt@austin.ibm.com>,
Ram Pai <linuxram@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] on-demand readahead
Date: 25 Apr 2007 16:37:41 +0200 [thread overview]
Message-ID: <p73odlc34ga.fsf@bingen.suse.de> (raw)
In-Reply-To: <377506695.54393@ustc.edu.cn>
Fengguang Wu <fengguang.wu@gmail.com> writes:
> OVERHEADS
>
> The new code reduced the overheads of
>
> - excessively calling the readahead routine on small sized reads
> (the current readahead code insists on seeing all requests)
>
> - doing a lot of pointless page-cache lookups for small cached files
> (the current readahead only turns itself off after 256 cache hits,
> unfortunately most files are < 1MB, so never see that chance)
Would it make sense to keep track in the AS if the file is completely in cache?
Then you could probably avoid a lot of these lookups for small in cache files
> --- linux-2.6.21-rc7-mm1.orig/mm/readahead.c
> +++ linux-2.6.21-rc7-mm1/mm/readahead.c
> @@ -733,6 +733,11 @@ unsigned long max_sane_readahead(unsigne
Quite simple patch, why is it that much simpler than your earlier patchkits?
Or is that on top of them?
You seem to have a lot of magic numbers. They probably all need symbols and
explanations.
Your white space also needs some work.
-Andi
next prev parent reply other threads:[~2007-04-25 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070425131133.GA26863@mail.ustc.edu.cn>
2007-04-25 13:11 ` [RFC][PATCH] on-demand readahead Fengguang Wu
2007-04-25 14:37 ` Andi Kleen [this message]
[not found] ` <20070425160400.GA27954@mail.ustc.edu.cn>
2007-04-25 16:04 ` Fengguang Wu
2007-04-26 6:58 ` Andrew Morton
2007-04-25 16:08 ` Andi Kleen
[not found] ` <20070426011655.GA6373@mail.ustc.edu.cn>
2007-04-26 1:16 ` Fengguang Wu
2007-05-02 10:02 ` [RFC] splice() and readahead interaction Eric Dumazet
[not found] ` <f6b15c890705050204l11045ba3w66c8c4ae0ac3407f@mail.gmail.com>
2007-05-07 21:54 ` Andrew Morton
2007-05-10 19:53 ` Eric Dumazet
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=p73odlc34ga.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=fengguang.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=oleg@tv-sign.ru \
--cc=slpratt@austin.ibm.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