From: Con Kolivas <kernel@kolivas.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Albert Cahalan <acahalan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [ckpatch][15/29] hz-no_default_250.patch
Date: Wed, 21 Jun 2006 14:53:09 +1000 [thread overview]
Message-ID: <200606211453.10239.kernel@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0606191351350.31576@yvahk01.tjqt.qr>
On Monday 19 June 2006 21:52, Jan Engelhardt wrote:
> >Yes I stored a family of these values and 864 was ~ the optimum for a high
> >value for desktops and ~84 for a low value but were unpopular for not
> > being
>
> 82 IIRC.
Ah yes here it is
HZ ticks/jiffie 1 second error (ppm)
---------------------------------------------------
82 14551 1.000000152 0.2
96 12429 1.000001829 1.8
209 5709 0.999999314 -0.7
363 3287 0.999999314 -0.7
519 2299 0.999999314 -0.7
864 1381 1.000001829 1.8
>
> >something decimally familiar. Also lots of code kind of broke with values
> >below 100 in the kernel.
>
> Ought to be fixed. Just like the code which assumed 100 Hz and broke during
> the initial switch to 1000, before we went back again to 250. :p
No impetus to fix them I guess since there is no way to configure the kernel
for sub 100 HZ configs without hacking it.
--
-ck
next prev parent reply other threads:[~2006-06-21 4:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 0:52 [ckpatch][15/29] hz-no_default_250.patch Albert Cahalan
2006-06-19 1:25 ` Con Kolivas
2006-06-19 11:52 ` Jan Engelhardt
2006-06-21 4:53 ` Con Kolivas [this message]
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=200606211453.10239.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=acahalan@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--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