Re: Measured overhead of timer interrupts

Khimenko Victor (khim@sch57.msk.ru)
Thu, 22 Jul 1999 23:12:22 +0400 (MSD)


In <19990722171109.A1783@fred.muc.de> Andi Kleen (ak@muc.de) wrote:
> On Thu, Jul 22, 1999 at 05:02:14PM +0200, Ingo Molnar wrote:
>>
>> On 22 Jul 1999, Andi Kleen wrote:
>>
>> > It is a kernel bug, HZ is not exported. Actually two, because none of
>> > the /proc should have used it as units, but that cannot be fixed anymore.
>>
>> why cannot it be fixed?

> because that would break the interface.

/proc interface are in permanent change. We should keep it consistent in one
stable kernel series but I see no reason to keep it consistent between major
kernel updates: quite a lot of things will be changed anyway.

>>
>> > It is easy to add a read-only sysctl for HZ though and make netstat use
>> > this, but this won't fix the trillions of other /proc parsers.
>>
>> we do not want to export HZ, why should we? HZ has no meaning to anything
>> else than the kernel. If the kernel exports HZ-dependent values into
>> /proc, then that has to be fixed. (yes it might be painful in some cases)
>> HZ might even go away in future kernels - what if we start using
>> nonperiodic timer interrupts?

> Actually, POSIX wants it (sysconf(_SC_CLK_TCK)). glibc currently returns
> the HZ value it was compiled with, but that is hardly satisfying.

This means that GLiBC must be fixed...

> I agree that the time related sysctls/proc files should be fixed, but I'm
> afraid it is too late.

/proc files are not a problem but sysctls... In which sysctls HZ is used in
such way that GLibC recompilation will not help ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/