From: dagenais Date: Fri, 4 Jul 2003 20:16:40 +0000 (+0000) Subject: git-svn-id: http://ltt.polymtl.ca/svn@101 04897980-b3bd-0310-b5e0-8ef037075253 X-Git-Tag: v0.12.20~3388 X-Git-Url: http://git.lttng.org./?a=commitdiff_plain;h=99416aeb3cc94191a24315867c6d4eac36305e18;hp=584db1461022b2a0092ebecc1c9b0c54d73dae9d;p=lttv.git git-svn-id: ltt.polymtl.ca/svn@101 04897980-b3bd-0310-b5e0-8ef037075253 --- diff --git a/ltt/branches/poly/doc/developer/discuss.html b/ltt/branches/poly/doc/developer/discuss.html new file mode 100644 index 00000000..b6159254 --- /dev/null +++ b/ltt/branches/poly/doc/developer/discuss.html @@ -0,0 +1,189 @@ + + + + Tracing Tools + + + +

Tracing Tools

+ +

Tracing is routinely used to help understanding the behavior and performance +of various aspects of the Linux kernel and associated drivers. +Many of the 80K+ printk statements in the Linux kernel +serve this purpose, although printk is relatively low +performance and unreliable. The small default printk buffer size coupled with +the low performance brings lost messages as soon as the volume becomes +significant. + +

For this reason, a number of drivers include their own tracing macros +and infrastructure. A quick search looking for TRACE and related keywords +in the Linux kernel source reveals some form of tracing in at least +the following files: + +