From: Matt Mackall <mpm@selenic.com>
To: "Moussa A. Ba" <moussa.a.ba@gmail.com>
Cc: linux-kernel@vger.kernel.org,
David Rientjes <rientjes@google.com>,
akpm@linux-foundation.org, adobriyan@gmail.com, mel@csn.ul.ie,
yinghan@google.com, npiggin@suse.de, jaredeh@gmail.com
Subject: Re: [PATCH 0/1] pagemap clear_refs: modify to specify anon or mapped vma clearing
Date: Thu, 23 Jul 2009 23:30:07 -0500 [thread overview]
Message-ID: <1248409807.24185.18.camel@calx> (raw)
In-Reply-To: <4A6930F5.3090008@gmail.com>
On Thu, 2009-07-23 at 20:56 -0700, Moussa A. Ba wrote:
> This patch makes the clear_refs proc interface a bit more versatile. It
> adds support for clearing either anonymous, file mapped pages or both.
>
> echo 1 > /proc/pid/clear_refs clears ANON pages
> echo 2 > /proc/pid/clear_refs clears file mapped pages
> echo 3 > /proc/pid/clear_refs clears all pages
>
> Selectively clearing pages has a measurable impact on performance as it
> decreases the number of page walks. We have been using this interface
> and this adds flexibility to the user space application implementing the
> reference clearing.
[adding David, the original instigator of clear_refs)
First, don't send 0 of 1 messages, especially for a single patch. It
makes Andrew curse and makes him more likely to consider other
employment possibilities. Instead incorporate highly useful info like
the above into your patch instead, preferably as docs and commit
descriptions.
Second, depending on how we've documented the behavior of this file,
this looks like it might break existing tools that are currently writing
'1' but expecting the behavior of '3'?
--
http://selenic.com : development and support for Mercurial and Linux
next prev parent reply other threads:[~2009-07-24 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 3:56 [PATCH 0/1] pagemap clear_refs: modify to specify anon or mapped vma clearing Moussa A. Ba
2009-07-24 4:30 ` Matt Mackall [this message]
2009-07-24 5:46 ` Moussa A. 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=1248409807.24185.18.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=rientjes@google.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