From: Paul Evans <paul@mxtelecom.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slow long-term increase in dirty pages
Date: Thu, 19 Mar 2009 14:51:18 +0000 [thread overview]
Message-ID: <20090319145118.32c5bfb0@nacelle.mxtelecom.com> (raw)
In-Reply-To: <20090319044751.GA12918@localhost>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
On Thu, 19 Mar 2009 12:47:51 +0800
Wu Fengguang <fengguang.wu@intel.com> wrote:
> The attached filecache patch shall help identify the dirty
> files/pages.
>
> Usage:
> # run patched kernel
> modprobe filecache
> cat /proc/filecache
>
> The dirty files will have the 'D' flag in its "state" field.
Wow, that looks very useful. I'll have a play with it and see if it
yields anything of interest.
Thanks,
--
Paul Evans <paul@mxtelecom.com>
Tel: +44 (0) 845 666 7778
Fax: +44 (0) 870 163 4694
http://www.mxtelecom.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-03-19 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 14:53 Slow long-term increase in dirty pages Paul Evans
2009-03-19 4:47 ` Wu Fengguang
2009-03-19 14:51 ` Paul Evans [this message]
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=20090319145118.32c5bfb0@nacelle.mxtelecom.com \
--to=paul@mxtelecom.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.