Re: [PATCH 2/4] ftrace - add function_duration tracer

[Ingo Molnar]

* Frank Ch. Eigler <fche@xxxxxxxxxx> wrote:

> Ingo Molnar <mingo@xxxxxxx> writes:
> 
> > [...]
> > Just off the top of my head we want to be able to trace:
> >
> >  - max irq service latencies for a given IRQ
> >  - max block IO completion latencies for a app
> >  - max TLB flush latencies in the system
> >  - max sys_open() latencies in a task
> >  - max fork()/exit() latencies in a workload
> >  - max scheduling latencies on a given CPU
> >  - max page fault latencies
> >  - max wakeup latencies for a given task
> >  - max memory allocation latencies
> >
> >  - ... and dozens and dozens of other things where there's a "start"
> >    and a "stop" event and where we want to measure the time between
> >    them.
> > [...]
> 
> FWIW, those who want to collect such measurements today can do so with 
> a few lines of systemtap script for each of the above.

Well, i dont think stap can do workload instrumentation. It can do 
system-wide (and user local / task local) - but can it do per task 
hierarchies?

Also, i dont think stap supports proper separation of per workload 
measurements either. I.e. can you write a script that will work properly 
even if multiple monitoring tools are running, each trying to measure 
latencies?

Also, i personally find built-in kernel functionality more trustable 
than dynamically built stap kernel modules that get inserted.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/