From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: acme@ghostprotocols.net, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Namhyung Kim <namhyung.kim@lge.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 2/3] perf trace: Add summary option to dump syscall statistics
Date: Wed, 9 Oct 2013 15:16:39 +0200 [thread overview]
Message-ID: <20131009131639.GB5459@krava.redhat.com> (raw)
In-Reply-To: <1381289214-24885-3-git-send-email-dsahern@gmail.com>
On Tue, Oct 08, 2013 at 09:26:53PM -0600, David Ahern wrote:
> When enabled dumps a summary of all syscalls by task with the usual
> statistics -- min, max, average and relative stddev. For example,
>
> make - 26341 : 3344 [ 17.4% ] 0.000 ms
>
> read : 52 0.000 4.802 0.644 30.08
> write : 20 0.004 0.036 0.010 21.72
> open : 24 0.003 0.046 0.014 23.68
> close : 64 0.002 0.055 0.008 22.53
> stat : 2714 0.002 0.222 0.004 4.47
> fstat : 18 0.001 0.041 0.006 46.26
> mmap : 30 0.003 0.009 0.006 5.71
> mprotect : 8 0.006 0.039 0.016 32.16
> munmap : 12 0.007 0.077 0.020 38.25
> brk : 48 0.002 0.014 0.004 10.18
> rt_sigaction : 18 0.002 0.002 0.002 2.11
> rt_sigprocmask : 60 0.002 0.128 0.010 32.88
> access : 2 0.006 0.006 0.006 0.00
> pipe : 12 0.004 0.048 0.013 35.98
> vfork : 34 0.448 0.980 0.692 3.04
> execve : 20 0.000 0.387 0.046 56.66
> wait4 : 34 0.017 9923.287 593.221 68.45
> fcntl : 8 0.001 0.041 0.013 48.79
> getdents : 48 0.002 0.079 0.013 19.62
> getcwd : 2 0.005 0.005 0.005 0.00
> chdir : 2 0.070 0.070 0.070 0.00
> getrlimit : 2 0.045 0.045 0.045 0.00
> arch_prctl : 2 0.002 0.002 0.002 0.00
> setrlimit : 2 0.002 0.002 0.002 0.00
> openat : 94 0.003 0.005 0.003 2.11
>
Should the syscalls columns be aligned with the data?
jirka
---
[ task - pid ] [ events ] [ ratio ] [ runtime ]
syscall count min max avg stddev
msec msec msec %
_____________________________________________________________________________
ls - 10994 : 530 [ 97.4% ] 0.000 ms
read : 18 0.000 0.016 0.003 25.51
open : 24 0.002 0.026 0.005 19.46
next prev parent reply other threads:[~2013-10-09 13:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 3:26 [PATCH 0/3] perf trace enhancements David Ahern
2013-10-09 3:26 ` [PATCH 1/3] perf util: Add findnew method to intlist - v2 David Ahern
2013-10-15 5:32 ` [tip:perf/core] perf util: Add findnew method to intlist tip-bot for David Ahern
2013-10-09 3:26 ` [PATCH 2/3] perf trace: Add summary option to dump syscall statistics David Ahern
2013-10-09 13:16 ` Jiri Olsa [this message]
2013-10-15 5:32 ` [tip:perf/core] " tip-bot for David Ahern
2013-10-09 3:26 ` [PATCH 3/3] perf record: mmap output file David Ahern
2013-10-09 5:59 ` Ingo Molnar
2013-10-15 14:04 ` David Ahern
2013-10-15 14:32 ` Arnaldo Carvalho de Melo
2013-10-15 14:38 ` Peter Zijlstra
2013-10-15 15:27 ` Ingo Molnar
2013-10-15 15:29 ` Peter Zijlstra
2013-10-15 15:30 ` David Ahern
2013-10-15 16:06 ` Ingo Molnar
2013-10-15 16:16 ` David Ahern
2013-10-16 7:11 ` Ingo Molnar
2013-10-15 16:37 ` Peter Zijlstra
2013-10-09 7:14 ` Mike Galbraith
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=20131009131639.GB5459@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.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
all inboxes | Powered by JetHome®