From: Liu Yuan <namei.unix@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
jaxboe@fusionio.com, akpm@linux-foundation.org,
fengguang.wu@intel.com
Subject: Re: [RFC PATCH 0/5] Add accountings for Page Cache
Date: Fri, 4 Mar 2011 09:55:36 +0800 [thread overview]
Message-ID: <AANLkTine1S9bjnqUCsYRhenYH6TUJTdOOQvdQ1nKY8Wv@mail.gmail.com> (raw)
In-Reply-To: <20110303104430.B93F.A69D9226@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
On Thu, Mar 3, 2011 at 9:50 AM, KOSAKI Motohiro <
kosaki.motohiro@jp.fujitsu.com> wrote:
> > [Summery]
> >
> > In order to evaluate page cache efficiency, system admins are happy to
> > know whether a block of data is cached for subsequent use, or whether
> > the page is read-in but seldom used. This patch extends an effort to
> > provide such kind of information. We adds three counters, which are
> > exported to the user space, for the Page Cache that is almost
> > transparent to the applications. This would benifit some heavy page
> > cache users that might try to tune the performance in hybrid storage
> > situation.
>
> I think you need to explain exact and concrete use-case. Typically,
> cache-hit ratio doesn't help administrator at all. because merely backup
> operation (eg. cp, dd, et al) makes prenty cache-miss. But it is no sign
> of memory shortage. Usually, vmscan stastics may help memroy utilization
> obzavation.
>
> Plus, as ingo said, you have to consider to use trancepoint framework
> at first. Because, it is zero cost if an admin don't enable such
> tracepoint.
>
>
Thanks very much for your comments.
Yeah, we'er going to try tracepoint and perf as Ingo said.
> At last, I don't think disk_stats have to have page cache stastics. It
> seems
> slightly layer violation.
>
> Thanks.
>
>
This is the starting point of the patch set, so I simply embedded the
structure into the existing infrastructure. This did saved me a lot of
effort because disk_stats is a good place to collect stats on _partition_
basis. Anyway, as you pointed out, this is kind of the mess.
Thanks,
Yuan
[-- Attachment #2: Type: text/html, Size: 2213 bytes --]
prev parent reply other threads:[~2011-03-04 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 8:37 noname noname
2011-03-03 1:50 ` KOSAKI Motohiro
2011-03-04 1:55 ` Liu Yuan [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=AANLkTine1S9bjnqUCsYRhenYH6TUJTdOOQvdQ1nKY8Wv@mail.gmail.com \
--to=namei.unix@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jaxboe@fusionio.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox