> 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. 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. -Andi -- 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/
