<div dir="ltr"><font face="georgia,serif"><br></font><br><div class="gmail_quote">On Wed, Jul 25, 2012 at 3:44 PM, Nadav Har'El <span dir="ltr"><<a href="mailto:nyh@math.technion.ac.il" target="_blank">nyh@math.technion.ac.il</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
USER_HZ is just used to fake the reports to user-space, pretending the<br>
resolution is of USER_HZ. The actual measured resolution is of<br>
CONFIG_HZ.<br></blockquote><div><br>Yes, but all this means is that the last digit of the result you get from times(2) or getruser(2) is probably significant - it is still 10ms resolution.<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im"><br>
> I am used to RedHat systems whose kernels normally come with HZ=100.</div></blockquote><div><br>I was wrong, actually, I just went to kernel's .config and it was 1000 on F15, CentOS6.2, and RHEL5.4 - I was fooled by USER_HZ, sorry.<br>
<br></div></div>-- <br>Oleg Goldshmidt | <a href="mailto:oleg@goldshmidt.org" target="_blank">pub@goldshmidt.org</a><br>
</div>