Re: dtrace users opinion solicited (timestamps)
- From: Robert Watson <rwatson@xxxxxxxxxxx>
- Date: Fri, 10 Jul 2009 12:12:37 +0100 (BST)
On Fri, 10 Jul 2009, Andriy Gapon wrote:
Thinking aloud - maybe we could always use one value of tsc_freq (or something like max_tsc_freq). This wouldn't give us correct timestamps when TSC frequency is changing, but it would give us something that is always proportional to TSC value and thus has its properties - monotonicity in the first place. And, of course, there is no problem when TSC frequency is constant.
Just a point from a user perspective: I find it useful (important even) to be able to compare timing between runs on the same box, and while that means I need to control for the frequency changing in an experimental sense, in as much as timestamp measurements in dtrace can be normalized, that would be helpful.
Robert N M Watson
Computer Laboratory
University of Cambridge
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- dtrace users opinion solicited (timestamps)
- From: Andriy Gapon
- Re: dtrace users opinion solicited (timestamps)
- From: Marius Nünnerich
- Re: dtrace users opinion solicited (timestamps)
- From: Andriy Gapon
- Re: dtrace users opinion solicited (timestamps)
- From: Tim Kientzle
- Re: dtrace users opinion solicited (timestamps)
- From: Andriy Gapon
- Re: dtrace users opinion solicited (timestamps)
- From: Andriy Gapon
- dtrace users opinion solicited (timestamps)
- Prev by Date: Re: Process stuck in vmmaps on 8.0-BETA1
- Next by Date: Re: 8.0-BETA1 bsdlabel broken?
- Previous by thread: Re: dtrace users opinion solicited (timestamps)
- Next by thread: Re: dtrace users opinion solicited (timestamps)
- Index(es):