From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: How to know HZ from userspace?
Date: 6 Jun 2001 13:55:53 -0700 [thread overview]
Message-ID: <9fm5cp$431$1@penguin.transmeta.com> (raw)
In-Reply-To: <20010530203725.H27719@corellia.laforge.distro.conectiva>
In article <20010530203725.H27719@corellia.laforge.distro.conectiva>,
Harald Welte <laforge@gnumonks.org> wrote:
>
>Is there any way to read out the compile-time HZ value of the kernel?
In 2.4.x, you'll get it on the stack as one of the ELF auxilliary
entries (AT_CLKTCK).
Strictly speaking that's the "frequency at which 'times()' counts", ie
the kernel CLOCKS_PER_SEC, not HZ. But from a user perspective the two
should hopefully always be the same (if any of the /proc fields etc
should really use CLOCKS_PER_SEC, not HZ).
Linus
next prev parent reply other threads:[~2001-06-06 20:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 23:37 How to know HZ from userspace? Harald Welte
2001-05-31 0:07 ` H. Peter Anvin
2001-05-31 0:22 ` Joel Becker
2001-05-31 0:24 ` Jonathan Lundell
2001-05-31 0:38 ` Joel Becker
2001-05-31 0:44 ` Jonathan Lundell
2001-05-31 1:02 ` Mike Castle
2001-05-31 17:12 ` Daniel Phillips
2001-05-31 1:17 ` Martin Dalecki
2001-05-31 3:23 ` Albert D. Cahalan
2001-06-01 1:57 ` Ralf Baechle
2001-06-01 4:12 ` H. Peter Anvin
2001-06-01 8:17 ` Chris Wedgwood
2001-05-31 3:40 ` Albert D. Cahalan
2001-05-31 15:52 ` Harald Welte
2001-05-31 17:06 ` H. Peter Anvin
2001-06-03 23:14 ` Erik Tews
2001-06-06 18:09 ` Tomas Telensky
2001-06-06 18:22 ` Harald Welte
2001-06-06 18:59 ` Tomas Telensky
2001-06-06 20:47 ` Harald Welte
2001-06-06 20:55 ` Linus Torvalds [this message]
2001-06-06 23:59 ` Chris Wedgwood
[not found] <XFMail.20010601083302.peterw@dascom.com.au>
2001-05-31 22:43 ` H. Peter Anvin
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='9fm5cp$431$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.