From: Matt Mackall <mpm@selenic.com>
To: "Moussa A. Ba" <moussa.a.ba@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Amerigo Wang <xiyou.wangcong@gmail.com>,
akpm@linux-foundation.org, adobriyan@gmail.com, mel@csn.ul.ie,
yinghan@google.com, npiggin@suse.de, jaredeh@gmail.com
Subject: Re: [PATCH 1/1] pagemap clear_refs: modify to specify anon or mapped vma clearing
Date: Mon, 27 Jul 2009 15:30:09 -0500 [thread overview]
Message-ID: <1248726609.1374.425.camel@calx> (raw)
In-Reply-To: <4A6E0BD6.50102@gmail.com>
On Mon, 2009-07-27 at 13:19 -0700, Moussa A. Ba wrote:
> This patch makes the clear_refs proc interface a bit more versatile.
> It adds support for clearing anonymous pages, file mapped pages or both.
>
> The clear_refs entry is used to reset the Referenced bits on virtual and
> physical pages associated with a process.
> echo 1 > /proc/PID/clear_refs clears all pages associated with the process
> echo 2 > /proc/PID/clear_refs clears anonymous pages only
> echo 3 > /proc/PID/clear_refs clears file mapped pages only
> Any other value written to the proc entry will clear all pages.
>
> Selective clearing the pages has a measurable impact on performance as it
> limits the number of page walks. We have been using this interface and this
> adds flexibility to the user user space application implementing the reference
> clearing.
Looks ok to me.
Acked-by: Matt Mackall <mpm@selenic.com>
--
http://selenic.com : development and support for Mercurial and Linux
next prev parent reply other threads:[~2009-07-27 20:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 3:57 [PATCH 1/1] pagemap clear_refs: modify to specify anon or mapped vma clearing Moussa A. Ba
2009-07-24 8:39 ` Amerigo Wang
2009-07-24 18:00 ` Moussa Ba
2009-07-27 20:19 ` Moussa A. Ba
2009-07-27 20:30 ` Matt Mackall [this message]
2009-07-27 20:57 ` David Rientjes
2009-07-27 22:14 ` Moussa Ba
2009-07-27 22:20 ` Matt Mackall
2009-07-27 22:49 ` David Rientjes
2009-07-27 23:38 ` Moussa Ba
2009-07-27 23:42 ` Moussa Ba
2009-07-27 23:58 ` David Rientjes
2009-07-28 3:24 ` Amerigo Wang
2009-07-28 16:44 ` Moussa A. Ba
2009-07-28 21:01 ` David Rientjes
2009-07-28 22:52 ` Moussa A. Ba
2009-07-28 23:52 ` Andrew Morton
2009-07-29 0:00 ` Moussa Ba
2009-07-29 14:58 ` Mel Gorman
2009-07-29 16:41 ` Matt Mackall
2009-07-30 19:21 ` Moussa Ba
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=1248726609.1374.425.camel@calx \
--to=mpm@selenic.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jaredeh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=moussa.a.ba@gmail.com \
--cc=npiggin@suse.de \
--cc=xiyou.wangcong@gmail.com \
--cc=yinghan@google.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