All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: chenggang.qin@gmail.com
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Namhyung Kim <namhyung@gmail.com>,
	Yanmin Zhang <yanmin.zhang@intel.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Mike Galbraith <efault@gmx.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Chenggang Qin <chenggang.qcg@alibaba-inc.com>
Subject: Re: [PATCH] perf script: Add a python script to statistic direct io behavior
Date: Thu, 31 Jan 2013 09:25:49 -0700	[thread overview]
Message-ID: <510A9B0D.6000503@gmail.com> (raw)
In-Reply-To: <510a34c6.c750420a.037e.74c6@mx.google.com>

Hi

On 1/31/13 2:08 AM, chenggang.qin@gmail.com wrote:
> From: chenggang.qin@gmail.com
>
> This patch depends on a prev patch: https://lkml.org/lkml/2013/1/29/47
>
> If the engineers want to analyze the direct io behavior of some applications
> without source code, perf tools with some appropriate tracepoints events in the
> VFS subsystem are excellent choice.
>
> Many database systems use their own page cache subsystems and use the direct IO
> to access the disks. Sometimes, the system engineers need to know the misses rate
> of the database system's page cache. This requirements can be satisfied by recording
> the database's file access behavior through the way of direct IO. So, we use 2
> tracepoint events to record the system wide's direct IO behavior. The 2 tracepoint
> events are:
> 1) vfs:direct_io_read
> 2) vfs:direct_io_write
> they were introduced by the patch: https://lkml.org/lkml/2013/1/29/47
> The script direct-io.py are introduced by this patch can record the 2 tracepoint
> events, analyse the sample data, and give a concise report.

What does this option provide that the I/O accounting with taskstats 
(e.g., iotop) does not provide?

David


  reply	other threads:[~2013-01-31 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  9:08 [PATCH] perf script: Add a python script to statistic direct io behavior chenggang.qin
2013-01-31 16:25 ` David Ahern [this message]
2013-02-01  1:56   ` Namhyung Kim

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=510A9B0D.6000503@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=chenggang.qcg@alibaba-inc.com \
    --cc=chenggang.qin@gmail.com \
    --cc=efault@gmx.de \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@gmail.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=yanmin.zhang@intel.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 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.