[ltt-dev] General Questions

[Mathieu Desnoyers]

I would recommend to first use lttv-gui -t /path_to_trace , which will
give you an overall view of what is happening in your trace.

Also see lttv -m textDump --help to get the switches that you can turn
on. Especially the "print field names" is useful to understand the trace.

Mathieu

* Kevin Harms (harms at mcs.anl.gov) wrote:
> 
>   Ok. Using baby steps I've got a working kernel and was able to do the following:
>   start trace
>   run test program
>   stop trace
> 
>   i now have the trace data. Can someone give me an idea of how to interpret the data? Is there documentation describing the output format of the textDump module?
> 
>   To summarize what I'm looking for. My test program called fsync 20 times. Most of the times these calls are "fast", but sometimes a few calls take 10x that. So i'd like to identify the slow call and see what's happening around it.
> 
> kevin
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68