From: Andreas Jaeger <aj@suse.de>
To: Rolf Fokkens <FokkensR@vertis.nl>
Cc: "'drepper@cygnus.com'" <drepper@cygnus.com>,
"'alan@lxorguk.ukuu.org.uk'" <alan@lxorguk.ukuu.org.uk>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: /proc/sys/kernel/hz
Date: Mon, 16 Jul 2001 20:34:23 +0200 [thread overview]
Message-ID: <u8snfwoh8w.fsf@gromit.moeb> (raw)
In-Reply-To: <938F7F15145BD311AECE00508B7152DB034C48DB@vts007.vertis.nl>
In-Reply-To: <938F7F15145BD311AECE00508B7152DB034C48DB@vts007.vertis.nl> (Rolf Fokkens's message of "Mon, 16 Jul 2001 20:00:19 +0200")
Rolf Fokkens <FokkensR@vertis.nl> writes:
> Ulrich Drepper <drepper@redhat.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
> patch
>>> just "publishes" the HZ constant in /proc/sys/kernel/hz.
>>
>>And what is wrong with
>> getconf CLK_TCK
>>or programmatically
>> hz = sysconf (_SC_CLK_TCK);
>
> In short: it doesn't work: it reads 100 while I changed it to 1024 in my
> kernel.
Then your kernel is broken, check AT_CLKTCK,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-07-16 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 18:00 PATCH: /proc/sys/kernel/hz Rolf Fokkens
2001-07-16 18:34 ` Andreas Jaeger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 19:24 Rolf Fokkens
2001-07-16 16:11 Rolf Fokkens
2001-07-16 16:50 ` Ulrich Drepper
2001-07-16 17:13 ` Kurt Garloff
2001-07-16 17:45 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u8snfwoh8w.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=FokkensR@vertis.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drepper@cygnus.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox