> 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().
Hmm so how about extending oprofile to always log the syscall number in the event logs (can be gotten from top of stack). I think given that you could reconstruct that data in the userland at least for single threads (not for work done on behalf of them in other threads; but I'm not sure you tried to solve that problem at all) The advantage is that it would be an generic mechanism that would work for all types of profiling. -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/
