From: Nick Piggin <nickpiggin@yahoo.com.au>
To: WU Fengguang <wfg@mail.ustc.edu.cn>
Cc: linux-kernel@vger.kernel.org, riel@redhat.com
Subject: Re: [RFC] use radix_tree for non-resident page tracking
Date: Mon, 10 Oct 2005 23:54:48 +1000 [thread overview]
Message-ID: <434A72A8.2000308@yahoo.com.au> (raw)
In-Reply-To: <20051010130705.GA5026@mail.ustc.edu.cn>
WU Fengguang wrote:
> Hi Rik,
> The CLOCK-Pro page replacement is quite appealing, and I'd like to
> contribute an idea: How about store bookkeeping info of dropped pages
> in-place in radix_tree?
>
> The slots in radix_tree_node can be used for bookkeeping data when
> the corresponding pages are dropped. When all pages in a radix_tree_node
> have been dropped, it is registered in an array/list for delayed
> reclaim.
>
> It would be fast and simple:
> - no cache-line pollution
> - no extra lock (with Nick Piggin's great RCU improvement)
Just a note if you are looking into this - the last version of the
radix-tree lockless readside patches I made public IIRC had some
bugs in them which I have since fixed.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-10-10 13:54 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 [this message]
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 ` [RFC] use radix_tree for non-resident page tracking WU Fengguang
2005-10-10 17:19 ` 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=434A72A8.2000308@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=wfg@mail.ustc.edu.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®