Andi Kleen wrote:
yes indeed; I sort of use the same infrastructure inside the scheduler; the
biggest
reason I felt I had to do something different was that I wanted to do per
process
data collection, so that you can see for a specific process what was going
on.
Wouldn't it have been easier then to just extend the sleep profiler to
oprofile? oprofile already has pid filters and can do per process
profiling.
it's more complex than that
On the other hand I'm not fully sure only doing per pid profiling
is that useful. After all often latencies come from asynchronous
threads (like kblockd). So a system level view is probably better
anyways.
another thing that the current profiling can't do, is to show what the system
is doing
when it hits the latency.. so someone calling fsync() will show up in the
waiting for
IO function, but not that it was due to an fsync().
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
