From: WU Fengguang <wfg@mail.ustc.edu.cn>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] use radix_tree for non-resident page tracking
Date: Tue, 11 Oct 2005 01:14:14 +0800 [thread overview]
Message-ID: <20051010171414.GA8194@mail.ustc.edu.cn> (raw)
In-Reply-To: <Pine.LNX.4.63.0510101237270.20944@cuia.boston.redhat.com>
On Mon, Oct 10, 2005 at 12:37:48PM -0400, Rik van Riel wrote:
> > > How are you going to get the inter-reference distance
> > > this way?
> >
> > How about taking down the current sum of `pgfree' in the slot?
>
> Sounds like a good idea to me. Definately worth a try!
Thanks.
I now realized that counters in struct zone should be better candidates.
And the slots may be used to calculate the real inter-reference distances
for dropped pages. For the present pages, we can either add entries to each
page, or to radix_tree_node. I suspect the latter is enough because it should
work well with sequential reads and sequential reads are the majority of page
activities and the main source of flushing.
--
WU Fengguang
Dept. of Automation
University of Science and Technology of China
Hefei, Anhui
next prev parent reply other threads:[~2005-10-10 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2005-10-10 13:07 ` [RFC] use radix_tree for non-resident page tracking\ Marcelo Tosatti
[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 [this message]
2005-10-10 17:19 ` [RFC] use radix_tree for non-resident page tracking Rik van Riel
2005-10-11 3:14 ` WU Fengguang
[not found] <20051010134345.C9E7CFB046@gatekeeper.ncic.ac.cn>
2005-10-10 15:21 ` 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=20051010171414.GA8194@mail.ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®