mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert Cahalan" <acahalan@gmail.com>
To: linux-kernel@vger.kernel.org, kernel@kolivas.org
Subject: Re: [ckpatch][15/29] hz-no_default_250.patch
Date: Sun, 18 Jun 2006 20:52:40 -0400	[thread overview]
Message-ID: <787b0d920606181752j4b7c7309t9c0ab9bf8da1537a@mail.gmail.com> (raw)

> Make 250 HZ a value that is not selected by default and give some
> better recommendations in help.

No, 250 is a good default.

We can't reliably do 1000. There are many systems, including both
laptops and servers, which have a BIOS that uses SMM/SMI to grab
the CPU for longer than a millisecond. We'd lose clock ticks if
we had HZ at 1000.

NTSC video is 59.94 fields per second. Though a sample rate of
double that would satisfy the Nyquest theory, in practice you
need to go to 4x to 5x the rate you want. This comes out to be
around 240 to 300 as a minimum.

Then there is the matter of picking a value that is very close
to being an integer factor of the standard PC clock. I don't
remember how well 250 did, but here is the code I once used
to compute such things:

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <float.h>
#include <math.h>

// 1189200.0 // AMD ELAN
// 1193182.0 // normal

#define PITHZ 1193182.0

double nearbyint(double x);

#define TARGET_MAX 1300 // was 15000
#define TARGET_MIN 240  // was 9

int main(int argc, char *argv[]){
  unsigned target = TARGET_MAX;
  while(--target>TARGET_MIN){
st:;
    unsigned setting = nearbyint(PITHZ / target);
    double actual = PITHZ / setting;
    double diff = actual - target;
    double perc = 100.0*diff/target;
//    if(target & 3) continue;
#if 1
    if(target!=1000 && target !=1024 && target!=100 && target!=400 &&
target!=600
      && target!=1200 && target!=240 && target!=300 && target!=800
      && target!=512 && target!=256 && target!=128)
      if(perc > 0.01 || perc < -0.01) continue;
#else
    {
    if(perc>-0.6 && perc<0.6) continue;
    }
#endif
    printf("%+11.8f %+10.6f %6u %5u %12.6f\n", perc, diff, setting,
target, actual);
  }
  if(target>105) {
    target = 100;
    goto st;
  }
  return 0;
}

             reply	other threads:[~2006-06-19  0:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  0:52 Albert Cahalan [this message]
2006-06-19  1:25 ` Con Kolivas
2006-06-19 11:52   ` Jan Engelhardt
2006-06-21  4:53     ` Con Kolivas
2006-06-19  1:30 ` Lee Revell
2006-06-19  1:52   ` Con Kolivas
  -- strict thread matches above, loose matches on Subject: below --
2006-06-18  7:32 Con Kolivas
2006-06-18  7:42 ` Willy Tarreau
2006-06-18 10:08   ` Con Kolivas
2006-06-18 15:03     ` Jan Engelhardt

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=787b0d920606181752j4b7c7309t9c0ab9bf8da1537a@mail.gmail.com \
    --to=acahalan@gmail.com \
    --cc=kernel@kolivas.org \
    --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®