Hi Krish, Yes that is the window I plan to use, the content will be switching between park/wait and locks, instead of showing them at the same time. This separates latency statistics into different point of views. For example, if file read operation uses lock a and b, write uses lock a and c, latencytop will show: file read 40% file write 60% and when the hotkey is pressed, latencytop will switch to: lock a 50% lock b 20% lock c 30% and another hotkey will switch back to the prior.
I'm not sure if it's possible to track the owners of all locks, it might not be easy to display it clearly, because a lock could be used by many processes at different times. However, if one lock seems to cause most of the latency in an application, user can then write a dtrace script to print all the wait/acquire/release details of that lock, which is useful in addition to the statistics shown by latencytop. -- This message posted from opensolaris.org _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
