On Mon, Feb 10, 2014 at 12:28:55PM -0500, Don Zickus wrote: > The data output is verbose and there are lots of data tables that interprit > the latencies > and data addresses in different ways to help see where bottlenecks might be > lying.
Would be good to see what the output looks like. What I haven't seen; and what I would find most useful; is using the IP + dwarf info to map it back to a data structure member. Since you're already using the PEBS data-source fields, you can also have a precise IP. For many cases its possible to reconstruct the exact data member the instruction is modifying. At that point you can do pahole like output of data structures, showing which members are 'hot' on misses etc. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
