On Tue, 2005-11-08 at 13:55 +1100, Benjamin Herrenschmidt wrote:
> Hi !
>
> I noticed that we set
>
> #define CLOCK_REALTIME_RES TICK_NSEC /* In nano seconds. */
>
> Unconditionally in kernel/posix-timer.c
>
> Doesn't that mean that we'll advertise to userland (via clock_getres) a
> resolution that is basically HZ ? We do get at lenght to get more
> precise (up to ns) resolution in practice on many architectures but we
> don't expose that to userland at all. Is this normal ?
This is the resolution which you can expect for timers (nanosleep and
interval timers) as the timers depend on the jiffy tick.
The resolution of the readout functions is not affected by this.
http://www.tglx.de/ktimers.html#writeup
should give you more information about that.
tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
