From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: "Maucci, Cyrille" <cyrille.maucci@hp.com>
Cc: Christoph Bartoschek <bartoschek@gmx.de>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Profiling a program's runtime
Date: Mon, 7 Feb 2011 18:38:31 -0200 [thread overview]
Message-ID: <20110207203831.GE4470@ghostprotocols.net> (raw)
In-Reply-To: <0E02F16954AF394BB163AEE50FDF548568FE033642@GVW1121EXC.americas.hpqcorp.net>
Em Fri, Feb 04, 2011 at 07:57:00PM +0000, Maucci, Cyrille escreveu:
> Yep. I was not promoting caliper here.
> I was just referring to it so that we may get an idea of what he'd like to see in 'perf' reports.
Right, useful pointers, thanks, barring patents, I think we can get that
with perf at some point.
Catering to I/O bound workloads is something that is in the radar, has
been experimented with and should resume development soon, please take a
look at the 'trace' description at:
http://lwn.net/Articles/415728/
The discussion also has lots of useful suggestions and insights.
It is an area that badly needs help to get the perf infrastructure to
the next level, beyong the current state of good (excellent?) CPU bound
profiling.
- Arnaldo
next prev parent reply other threads:[~2011-02-07 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 14:38 Profiling a program's runtime Christoph Bartoschek
2011-02-04 17:16 ` Frederic Weisbecker
2011-02-04 17:41 ` Christoph Bartoschek
2011-02-04 17:47 ` Frederic Weisbecker
2011-02-04 18:10 ` David Ahern
2011-02-04 18:33 ` Maucci, Cyrille
2011-02-04 19:48 ` Christoph Bartoschek
2011-02-04 19:57 ` Maucci, Cyrille
2011-02-07 20:38 ` Arnaldo Carvalho de Melo [this message]
2011-02-04 19:51 ` Christoph Bartoschek
2011-02-05 0:56 ` David Ahern
2011-02-04 19:24 ` Christoph Bartoschek
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=20110207203831.GE4470@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=bartoschek@gmx.de \
--cc=cyrille.maucci@hp.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).