From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Zanussi <zanussi@us.ibm.com>
Cc: ltt-dev@shafik.org, Michel Dagenais <michel.dagenais@polymtl.ca>
Subject: [PATCH x/16] LTTng : Linux Trace Toolkit Next Generation 0.5.95, kernel 2.6.17
Date: Wed, 30 Aug 2006 19:10:46 -0400 [thread overview]
Message-ID: <20060830231045.GA17079@Krystal> (raw)
Hi,
Following my presentation "The LTTng Tracer : a low impact performance and
behavior monitor for GNU/Linux" at OLS2006, I think the interest shown by the
community for the LTTng tracer makes it worthy to be announced to LKML so it canbenefit from your input and be eventually mainlined.
Through the discussion some of us had at OLS this year, the emergence of many
ad-hoc tracing tools (RT-preempt latency tracer, Block I/O subsystem tracer)
and of many tracing projects (SystemTAP, LKST, KFT, LTTng) shows the need for
a solid tracing infrastructure, which has been the focus of my work.
The LTTng core fulfills primarily the following goals :
- Serializing information in event records
- Serializing event records
- Must be trivial to use by subsystem maintainers
- Usable from any execution context
- Relatively simple, minimum side effect
- Identity of the event record
- Flexible types in the event record
- Tracing control mechanism
The project is described in my paper, available in the OLS2006 proceedings or atthe following URL : http://ltt.polymtl.ca/papers/desnoyers-ols2006.pdf. More
information is available at http://ltt.polymtl.ca (see the QUICKSTART guide to
learn how to have the complete set of tools ready to be used).
I hope such an infrastructure will incite kernel developers to instrument
their own subsystem.
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
reply other threads:[~2006-08-30 23:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060830231045.GA17079@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=zanussi@us.ibm.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