From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Valdis.Kletnieks@vt.edu,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org,
Michael Boerner <michael@boernerconsulting.com>
Subject: Re: [PATCH] Combine instrumentation menus in kernel/Kconfig.instrumentation
Date: Wed, 19 Sep 2007 07:45:18 -0400 [thread overview]
Message-ID: <20070919114516.GH15500@Krystal> (raw)
In-Reply-To: <Pine.LNX.4.64.0709190731570.16870@localhost.localdomain>
* Robert P. J. Day (rpjday@mindspring.com) wrote:
> On Wed, 19 Sep 2007, Mathieu Desnoyers wrote:
>
> > * Valdis.Kletnieks@vt.edu (Valdis.Kletnieks@vt.edu) wrote:
>
> > > Ahh, LTT. *that* I recognize. Yeah, I count that as *one flavor*
> > > of instrumentation. :)
>
> mathieu clarified this in a previous email to me, but is LTT not
> entirely superseded by LTT-ng? just curious.
>
Yes, LTTng supersedes LTT. It provides the ability to extract traces
across execution layers (hypervisor, kernel, userspace) to perform
performance analysis and debugging of applications at the system level.
LTTng's approach differs from LTT in that it allows completely
customizable instrumentation. We chose to provide that based on the
previous LTT experience, where we have seen that adding instrumentation
is very often required when digging deeply into a problem.
Mathieu
> rday
> --
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry
> Waterloo, Ontario, CANADA
>
> http://crashcourse.ca
> ========================================================================
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2007-09-19 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 21:12 [PATCH] Combine instrumentation menus in kernel/Kconfig.instrumentation Mathieu Desnoyers
2007-09-18 21:45 ` Valdis.Kletnieks
2007-09-19 1:06 ` Mathieu Desnoyers
2007-09-19 5:57 ` Valdis.Kletnieks
2007-09-19 11:20 ` Mathieu Desnoyers
2007-09-19 11:33 ` Robert P. J. Day
2007-09-19 11:45 ` Mathieu Desnoyers [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 18:45 Mathieu Desnoyers
2007-09-18 18:37 ` Randy Dunlap
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=20070919114516.GH15500@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@boernerconsulting.com \
--cc=randy.dunlap@oracle.com \
--cc=rpjday@mindspring.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