From: Joel Becker <jlbec@evilplan.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to know HZ from userspace?
Date: Thu, 31 May 2001 01:22:10 +0100 [thread overview]
Message-ID: <20010531012210.I16761@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20010530203725.H27719@corellia.laforge.distro.conectiva> <9f41vq$our$1@cesium.transmeta.com>
In-Reply-To: <9f41vq$our$1@cesium.transmeta.com>; from hpa@zytor.com on Wed, May 30, 2001 at 05:07:22PM -0700
On Wed, May 30, 2001 at 05:07:22PM -0700, H. Peter Anvin wrote:
> Followup to: <20010530203725.H27719@corellia.laforge.distro.conectiva>
> By author: Harald Welte <laforge@gnumonks.org>
> In newsgroup: linux.dev.kernel
> > Is there any way to read out the compile-time HZ value of the kernel?
>
> Yes, but that's because the interfaces are broken. The decision has
> been that these values should be exported using the default HZ for the
> architecture, and that it is the kernel's responsibility to scale them
> when HZ != USER_HZ. I don't know if any work has been done in this
> area.
Pardon, but that still seems broken to me. USER_HZ shouldn't
matter to the architecture either. I would think that if
'echo 10 > /proc/foo/icmp_foo' sets a timeout of 10ms on alpha, it
should also do so on x86, sparc, and mips. Why should the userspace
implementation *ever* have to know the 'architecture HZ', the 'real HZ'
or anything of the kind?
Joel
--
"I'm drifting and drifting
Just like a ship out on the sea.
Cause I ain't got nobody, baby,
In this world to care for me."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2001-05-31 0:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 23:37 Harald Welte
2001-05-31 0:07 ` H. Peter Anvin
2001-05-31 0:22 ` Joel Becker [this message]
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 0:24 ` Jonathan Lundell
2001-05-31 0:38 ` Joel Becker
2001-05-31 1:17 ` Martin Dalecki
2001-05-31 0:44 ` Jonathan Lundell
2001-05-31 1:02 ` Mike Castle
2001-05-31 17:12 ` Daniel Phillips
2001-05-31 3:23 ` Albert D. Cahalan
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
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=20010531012210.I16761@parcelfarce.linux.theplanet.co.uk \
--to=jlbec@evilplan.org \
--cc=hpa@zytor.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
all inboxes | Powered by JetHome®