[lkml]   [2012]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: clock_getres() and real resolution
On Wed, Feb 08, 2012 at 08:31:03AM -0800, Dmitry Antipov wrote:
> IIUC, an idea behind clock_getres() is to give a hint about the resolution of
> specified clock. This hint may be used by an application programmer to check whether
> this clock is suitable for a some purpose. So why clock_getres() always returns
> something like {0, 1} (if hrtimers are enabled) regardless of the underlying platform's
> real numbers?

I think "resolution" does not mean tick duration, but rather the finest timer unit.


 \ /
  Last update: 2012-02-09 06:15    [W:0.044 / U:3.136 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site