Hi Lejun,
Yes, I think we can display the data from the "adaptive-block" probe as a
separate count so that users will know if a thread was blocked on an adaptive
lock.
I will open CRs for this and other enhancements that I mentioned in the mail.
Thanks,
Krish
--
This message posted from ope
Hi Krishnendu,
Thank you for these excellent suggestions, I think they will improve the
usability of LatencyTOP.
For the adaptive-block probe, it is possible to add it to the D script, but
when it happens, the sleep time will be counted by both adaptive-block and the
off-cpu/on-cpu probes in L
Thanks Eric for your thoughts. In order to answer these questions better, I am
wondering whether the tool should make use of another dtrace probe :
adaptive-block -> this tells us how much time the thread is sleeping on
an adaptive lock
Also, I have some suggestions regarding the look-a
Krishnendu Sadhukhan wrote:
The LatencyTOP team is seeking valuable feedback on the tool, and possible any
user requirements that may not have been implemented yet, in order to make this
tool fulfill the needs of a wide range of user base. All information about the
tool is available on the Lat
The LatencyTOP team is seeking valuable feedback on the tool, and possible any
user requirements that may not have been implemented yet, in order to make this
tool fulfill the needs of a wide range of user base. All information about the
tool is available on the LatencyTOP project page at
http:
