Re: HZ question

[Mark Hounschell <markh@compro.net>]

linux-os (Dick Johnson) wrote:
> On Tue, 13 Sep 2005, Mark Hounschell wrote:
> 
>>I need to know the kernels value of HZ in a userland app.
>>
>>getconf CLK_TCK
>>     and
>>hz = sysconf (_SC_CLK_TCK)
>>
>>both seem to return CLOCKS_PER_SEC which is defined as USER_HZ which is
>>defined as 100.
>>
>>include/asm/param.h:
>>
>>#ifdef __KERNEL__
>># define HZ       1000   /* Internal kernel timer frequency */
>># define USER_HZ  100    /* .. some user interfaces are in "ticks" */
>># define CLOCKS_PER_SEC  (USER_HZ)       /* like times() */
>>#endif
>>
>>Thanks in advance for any help
>>Mark
> 
> You are not supposed to 'tear apart' user-mode headers. In particular
> you are not supposed to use anything in /usr/include/bits, /usr/include/asm,
> or /usr/include/linux in user-mode programs. These are not POSIX headers.
>

This was a kernel header used for reference. I'm not including them.


> If a user-mode program needs to know HZ, it is very, very, broken.
> HZ is some kernel timeout tick which doesn't relate to anything
> a user program needs to know.
> 

Most if not all userland delay calls rely on HZ value in some way or 
another. The minimum reliable delay you can get is one (kernel)HZ. A 
program that needs an acurrate delay for a time shorter that one 
(kernel)HZ may have an alternative if it knows that HZ is greater the 
the requested delay. So to say my program is broken because it wants to 
know the limitations of my OS/kernel is kind of far fetched.


> This is a problem and is why we should have a kernel system-call
> that returns the HZ value. I asked about this several years ago
> and its inclusion was flatly refused because of what I quoted
> above. Perhaps now that HZ are dynamic, it would be posasible to
> add that system call.
> 

I'll second that. I thought sysconf(_SC_CLK_TCK) was supposed to be that 
call.

> Note, that on this particular kernel, at this phase of the moon...
> This program returns the HZ value.
> 
> #include <stdio.h>
> #include <unistd.h>
> 
> int main()
> {
>      printf("%d\n", sysconf(_SC_CLK_TCK));
>      return 0;
> }
> 
> 
> 

No it does not. It returns USER_HZ. At least on any 2.6.12 and <.

Mark