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, l
Regarding the questions Eric raised, I think we can answer "What/who is it
waiting on" by adding a new view like:
Process XYZ:Total: 80
msec
Type:Name Count AverageMax
Mutex:ff02532845f
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
Hi Rafael,
Thank you for your suggestions :) Please see my comments below.
> Hi Lejun
>
> The design doc looks good, here are my comments.
>
> Sec 2.2: Is there a limit to the number of rules the
> user can specify in
> the configuration file?
There's no explicit limit. The rule matching will
Hi all,
Here's the design document for LatencyTop. Comments are welcome. Thanks.
--
This message posted from opensolaris.org LatencyTOP High Level Design Document
Zhu, Lejun(lejun@intel.com)
