[PATCH] ppc32: add CONFIG_HZ
Paul Mackerras
paulus at samba.org
Sun Aug 28 12:19:47 EST 2005
Dan Malek writes:
> Yes, the application interfaces are all defined as 100 Hz (10 mSec).
> If the POSIX timer implementation is done properly, it should be
> possible to determine the timer parameters to eliminate this, but
> I doubt any applications do this. They all assume 10 mSec :-)
There are in fact only a few interfaces that work in terms of "clock
ticks", which are 10ms as far as userspace is concerned. I can think
of times() and that's about it. There are also the si_utime and
si_stime fields of the siginfo_t that comes along with a SIGCHLD. All
of those are about reporting CPU time used, not about specifying
timeouts.
All of the interfaces that specify timeouts or control timers use
struct timeval (seconds + microseconds) or struct timespec (seconds +
nanoseconds), or else use milliseconds (e.g. poll()).
Paul.
More information about the Linuxppc-dev
mailing list