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 11:14:20 +0800 [thread overview]
Message-ID: <20051011031420.GA5328@mail.ustc.edu.cn> (raw)
In-Reply-To: <Pine.LNX.4.63.0510101311280.20944@cuia.boston.redhat.com>
On Mon, Oct 10, 2005 at 01:19:34PM -0400, Rik van Riel wrote:
> On Tue, 11 Oct 2005, WU Fengguang wrote:
>
> > I now realized that counters in struct zone should be better candidates.
>
> Probably not, since a logical page could be swapped out from one
> memory zone and paged back in to another.
I managed to keep the page aging of each zone balanced in the patch:
http://marc.theaimsgroup.com/?l=linux-kernel&m=112856866504476&w=2
Zones in nearby nodes are also made balanced somewhat.
The ages are currently measured by accumulated number of pages pushed into lru.
I wonder that has the side effect of making other activities of each zone
roughly balanced, too. It needs some testing. If so, we can just sum up counters
of each zone in the current node.
--
WU Fengguang
Dept. of Automation
University of Science and Technology of China
Hefei, Anhui
next prev parent reply other threads:[~2005-10-11 3:14 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 ` [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 [this message]
[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=20051011031420.GA5328@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®