The macro CLOCKS_PER_SEC is used for AT_CLKTCK, and for some architectures
there actually _is_ a relationship between CLOCKS_PER_SEC and HZ, and for
some there is _not_ (linux/include/asm-*/param.h).
For i386 the relation apparently _is_ there. For IA64 there's the assumption
however that that the relation is _not_ there, the kernel assumes that it's
100 HZ for ia32 _always_. Weird.
Still leaves me wondering about procps.
From: Andreas Jaeger [mailto:firstname.lastname@example.org]
Sent: Monday, July 16, 2001 8:34 PM
To: Rolf Fokkens
Cc: 'email@example.com'; 'firstname.lastname@example.org';
Subject: Re: PATCH: /proc/sys/kernel/hz
Rolf Fokkens <FokkensR@vertis.nl> writes:
> Ulrich Drepper <email@example.com> writes:
>>> Some software (like procps) needs the HZ constant in the kernel. It's
>>> sometimes determined by counting jiffies during a second. The attached
>>> just "publishes" the HZ constant in /proc/sys/kernel/hz.
>>And what is wrong with
>> getconf CLK_TCK
>> hz = sysconf (_SC_CLK_TCK);
> In short: it doesn't work: it reads 100 while I changed it to 1024 in my
Then your kernel is broken, check AT_CLKTCK,
-- Andreas Jaeger SuSE Labs firstname.lastname@example.org private email@example.com http://www.suse.de/~aj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 23 2001 - 21:00:07 EST