mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to know HZ from userspace?
Date: Thu, 31 May 2001 12:52:25 -0300	[thread overview]
Message-ID: <20010531125225.O27719@corellia.laforge.distro.conectiva> (raw)
In-Reply-To: <20010530203725.H27719@corellia.laforge.distro.conectiva> <200105310340.f4V3eVF244481@saturn.cs.uml.edu>
In-Reply-To: <200105310340.f4V3eVF244481@saturn.cs.uml.edu>; from acahalan@cs.uml.edu on Wed, May 30, 2001 at 11:40:30PM -0400

On Wed, May 30, 2001 at 11:40:30PM -0400, Albert D. Cahalan wrote:
> Harald Welte writes:
> 
> > Is there any way to read out the compile-time HZ value of the kernel?
> > 
> > I had a brief look at /proc/* and didn't find anything.
> 
> Look again, this time with a sick mind. Got your barf bag?
> Kubys made me do it.

;) 

First of all thanks for your recommended solution.

>   /* actual values used by 2.4 kernels: 32 64 100 128 1000 1024 1200 */
>   switch(h){
>   case   30 ...   34 :  Hertz =   32; break; /* ia64 emulator */
>   case   48 ...   52 :  Hertz =   50; break;
>   case   58 ...   62 :  Hertz =   60; break;
>   case   63 ...   65 :  Hertz =   64; break; /* StrongARM /Shark */
>   case   95 ...  105 :  Hertz =  100; break; /* normal Linux */
>   case  124 ...  132 :  Hertz =  128; break; /* MIPS, ARM */
>   case  195 ...  204 :  Hertz =  200; break; /* normal << 1 */
>   case  253 ...  260 :  Hertz =  256; break;
>   case  393 ...  408 :  Hertz =  400; break; /* normal << 2 */
>   case  790 ...  808 :  Hertz =  800; break; /* normal << 3 */
>   case  990 ... 1010 :  Hertz = 1000; break; /* ARM */
>   case 1015 ... 1035 :  Hertz = 1024; break; /* Alpha, ia64 */
>   case 1180 ... 1220 :  Hertz = 1200; break; /* Alpha */

As this is some kind of solution, it is not really generic enough. 
Nobody is prevented from setting his Hz value to 500 or any number coming
to his mind (i.e. when he wants to do something nasty with TBF of tc).

And if you actually look at x86-user-mode-linux, it is 20...


-- 
Live long and prosper
- Harald Welte / laforge@gnumonks.org               http://www.gnumonks.org/
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M- 
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)

  reply	other threads:[~2001-05-31 16:03 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
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 [this message]
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=20010531125225.O27719@corellia.laforge.distro.conectiva \
    --to=laforge@gnumonks.org \
    --cc=acahalan@cs.uml.edu \
    --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®