Hi Phil,
When you say clock_getres() is broken on the sub-us level, do you mean
that 4000250 value you got? I'm not sure that's broken. It may not be
what you want, but it may be correct. Isn't it possible that's as
close as they can get to 250 Hertz with the hardware they have?
- Corey
Philip Mucci <[EMAIL PROTECTED]> wrote on 07/07/2008 12:08:29 PM:
> Ok, I'l bite...
>
> But here, how does one obtain the clock resolution easily? sysconf()
> is broken and clock_getres() is also, at least at the sub-us level,
> plus it requires users link with -lrt. If we go the latter route, at
> least the value should be correct...not what it is now.
>
> There must be a better answer...another sysfs file?
>
> Phil
>
> On Jul 7, 2008, at 8:29 PM, Corey J Ashford wrote:?
>
> Having dealt with this sort of "request some interval value and
> pray" interface in the past, I'd much prefer the
> idea of using a multiple of an obtainable clock resolution.
>
> - Corey
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
perfmon2-devel mailing list
perfmon2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
