On Tue, 2007-11-06 at 16:37 -0800, Neelam wrote: > I am using timestamp() in DTrace for timing some events, in particular > duration of a lock (i.e. time elapsed between the acquisition and release of > a mutex lock). I am getting pretty high numbers. But when I time the lock by > explicitly using timing functions such as gethrtime(), I get pretty low > numbers. Does this mean timestamp() doesn't give us the accurate > measurements? What are the alternatives?
We had similar issues with gethrtime on 64bit architectures. Where the result was truncated to 32 bits. Of course, it is hard to tell whether it is the same problem or not without seeing your D script. Thanks, Roman. _______________________________________________ dtrace-discuss mailing list [email protected]
