From: "Frank Ch. Eigler" <fche@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: David Ahern <dsahern@gmail.com>,
"Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: timing information with perf
Date: Tue, 17 Nov 2015 09:04:04 -0500 [thread overview]
Message-ID: <20151117140404.GH25870@redhat.com> (raw)
In-Reply-To: <20151117133959.GN22729@kernel.org>
Hi -
> > systemtap compiles down to native code, so execution is very fast and
> > CPU consumption is not a problem (better than streaming to userspace &
> > processing there).
>
> That "better' is also not a simple answer, as there are several factors
> :-)
(I was referring only to CPU consumption in that context.)
> Anyway, those are different methods, applicable to different scenarios
> and sets of constraints, sometimes only one of these tools can be used,
> due to these constraints, sometimes one can try several and see how they
> fare.
That's 100% right.
- FChE
prev parent reply other threads:[~2015-11-17 14:04 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
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 [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=20151117140404.GH25870@redhat.com \
--to=fche@redhat.com \
--cc=Olga.Kornievskaia@netapp.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--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).