From: David Ahern <dsahern@gmail.com>
To: "Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: timing information with perf
Date: Thu, 12 Nov 2015 16:22:35 -0700 [thread overview]
Message-ID: <56451F3B.8020509@gmail.com> (raw)
In-Reply-To: <21ECAC65-E51A-4430-A499-FFE216BF856B@netapp.com>
On 11/12/15 4:09 PM, Kornievskaia, Olga wrote:
> Just to elaborate further, what I’m interested in timings of NFS operations, so I’m not using any new tracepoints, but just the ones that are present in the code. However since NFS doesn’t various things outside of the process calling into NFS then will “perf trace” still work?
>
> I’m using “perf record -e ‘nfs4:*’,’nfs:*’ -ag” command to generate tracing info. That captures tracepoints executed by the application as well as the kernel threads that do asynchronous IO.
Do you really need callchains? (-g option)
After the perf-record run perf-script to dump the samples. Pipe that
into an awk script (or python or bash or ...) and you can compute what
you want.
next prev parent reply other threads:[~2015-11-12 23:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 21:07 timing information with perf Kornievskaia, Olga
2015-11-12 21:57 ` Arnaldo Carvalho de Melo
2015-11-12 22:04 ` Arnaldo Carvalho de Melo
2015-11-12 23:19 ` David Ahern
2015-11-12 23:09 ` Kornievskaia, Olga
2015-11-12 23:22 ` David Ahern [this message]
2015-11-12 23:34 ` Arnaldo Carvalho de Melo
2015-11-13 17:01 ` Kornievskaia, Olga
2015-11-13 19:47 ` Arnaldo Carvalho de Melo
2015-11-13 21:57 ` Kornievskaia, Olga
2015-11-16 18:08 ` Frank Ch. Eigler
2015-11-17 0:12 ` Arnaldo Carvalho de Melo
2015-11-17 0:30 ` Frank Ch. Eigler
2015-11-17 1:31 ` Arnaldo Carvalho de Melo
2015-11-17 3:57 ` David Ahern
2015-11-17 13:31 ` Frank Ch. Eigler
2015-11-17 13:39 ` Arnaldo Carvalho de Melo
2015-11-17 14:04 ` Frank Ch. Eigler
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=56451F3B.8020509@gmail.com \
--to=dsahern@gmail.com \
--cc=Olga.Kornievskaia@netapp.com \
--cc=acme@kernel.org \
--cc=linux-perf-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).