From: WU Fengguang <wfg@mail.ustc.edu.cn>
To: Yingchao Zhou <yc_zhou@ncic.ac.cn>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] use radix_tree for non-resident page tracking
Date: Mon, 10 Oct 2005 23:21:43 +0800 [thread overview]
Message-ID: <20051010152141.GA6714@mail.ustc.edu.cn> (raw)
In-Reply-To: <20051010134345.C9E7CFB046@gatekeeper.ncic.ac.cn>
On Mon, Oct 10, 2005 at 09:37:47PM +0800, Yingchao Zhou wrote:
> The paper "The Performance Impact of Kernel Prefetching On Buffer
> Cache Replacement Algorithms" appeared in SIGMETRICS05 gives some
> interesting relative results of replacement algorithm when taking
Thanks for the information, it should help my work on read-ahead.
I noticed similar problem when testing read-ahead behavior for fs-on-loop.
The basic conclusion is read-ahead in the block device level can
complement file level read-ahead, for the latter does not do inter-file
read-ahead. But it has to be limited/conservative, because the risk of
cache miss is much higher.
> into account of prefetching. How about the situation in CLOCK-Pro
> project?
Sorry, I'm new to CLOCK-Pro, too...
--
WU Fengguang
Dept. of Automation
University of Science and Technology of China
Hefei, Anhui
next parent reply other threads:[~2005-10-10 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051010134345.C9E7CFB046@gatekeeper.ncic.ac.cn>
2005-10-10 15:21 ` WU Fengguang [this message]
2005-10-10 13:07 WU Fengguang
2005-10-10 13:54 ` Nick Piggin
2005-10-10 14:00 ` Rik van Riel
2005-10-10 16:20 ` WU Fengguang
[not found] ` <20051010161704.GA7679@mail.ustc.edu.cn>
[not found] ` <Pine.LNX.4.63.0510101237270.20944@cuia.boston.redhat.com>
2005-10-10 17:14 ` WU Fengguang
2005-10-10 17:19 ` Rik van Riel
2005-10-11 3:14 ` 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=20051010152141.GA6714@mail.ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=yc_zhou@ncic.ac.cn \
/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
all inboxes | Powered by JetHome®