From: Albert Cahalan <albert@users.sf.net>
To: john stultz <johnstul@us.ibm.com>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>,
george anzinger <george@mvista.com>,
Andrew Morton OSDL <akpm@osdl.org>,
Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>,
albert@users.sourceforge.net, hirofumi@mail.parknet.co.jp,
lkml <linux-kernel@vger.kernel.org>,
voland@dmz.com.pl, nicolas.george@ens.fr,
david+powerix@blue-labs.org
Subject: Re: [PATCH] Re: boot time, process start time, and NOW time
Date: 30 Aug 2004 20:37:34 -0400 [thread overview]
Message-ID: <1093912654.434.7022.camel@cube> (raw)
In-Reply-To: <1093909116.14662.105.camel@cog.beaverton.ibm.com>
On Mon, 2004-08-30 at 19:38, john stultz wrote:
> This isn't going to happen instantly by any means. I'm trying to
> get the time of day rework finished as soon as I can, but I've
> got the day job to do as well. In the mean time, we can staple gun
> any user visible exported HZ/jiffies values so they are accurate
> (using ACTHZ or gettimeofday), and also look into changing HZ to a
> less error-ful value. HZ=1001 has been suggested and looks quite
> promising (although /net/schec/estimator.c wants a power of 4).
Well, pick something else. Here's a list of choices with
error under 0.0025%, in the 240..1300 range, that can be
evenly divided by four.
Dropping back a bit would be good, to better tolerate
systems with firmware that steals enough time to cause
lost clock ticks.
I like 400, 488, and 556. 864 and 1112 are decent too.
It might be useful having 400 as a multiple of 100.
I don't think /net/sched/estimator.c needs such
great accuracy. If that were sacrificed, one could
do much better with HZ at 363, 519, or 627.
%error HZerror PIT# HZ actual
-0.00217900 -0.007234 3594 332 331.992766
-0.00217900 -0.014469 1797 664 663.985531
-0.00217900 -0.021703 1198 996 995.978297
-0.00184378 -0.014676 1499 796 795.985324
-0.00150855 -0.004586 3925 304 303.995414
-0.00150855 -0.005732 3140 380 379.994268
-0.00150855 -0.006034 2983 400 399.993966
-0.00150855 -0.009474 1900 628 627.990526
-0.00150855 -0.011465 1570 760 759.988535
-0.00150855 -0.018947 950 1256 1255.981053
-0.00083809 -0.002581 3874 308 307.997419
-0.00083809 -0.003051 3278 364 363.996949
-0.00083809 -0.004794 2086 572 571.995206
-0.00083809 -0.004995 2002 596 595.995005
-0.00083809 -0.005163 1937 616 615.994837
-0.00083809 -0.006101 1639 728 727.993899
-0.00083809 -0.009588 1043 1144 1143.990412
-0.00083809 -0.009990 1001 1192 1191.990010
-0.00050285 -0.006376 941 1268 1267.993624
-0.00016762 -0.000483 4143 288 287.999517
-0.00016762 -0.000724 2762 432 431.999276
-0.00016762 -0.001448 1381 864 863.998552
+0.00050286 +0.001488 4031 296 296.001488
+0.00050286 +0.002796 2146 556 556.002796
+0.00050286 +0.005592 1073 1112 1112.005592
+0.00150859 +0.018163 991 1204 1204.018163
+0.00184384 +0.004499 4890 244 244.004499
+0.00184384 +0.008998 2445 488 488.008998
+0.00184384 +0.012022 1830 652 652.012022
+0.00184384 +0.013497 1630 732 732.013497
+0.00184384 +0.022495 978 1220 1220.022495
+0.00217909 +0.027282 953 1252 1252.027282
next prev parent reply other threads:[~2004-08-31 0:39 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 23:57 boot time, process start time, and NOW time Albert Cahalan
2004-06-28 17:56 ` OGAWA Hirofumi
2004-08-16 19:41 ` Andrew Morton
2004-08-16 21:49 ` john stultz
2004-08-16 23:08 ` Tim Schmielau
2004-08-16 23:56 ` Tim Schmielau
2004-08-17 0:21 ` john stultz
2004-08-17 0:37 ` George Anzinger
2004-08-17 0:49 ` john stultz
2004-08-17 0:31 ` George Anzinger
2004-08-16 22:32 ` Albert Cahalan
2004-08-17 1:26 ` George Anzinger
2004-08-16 23:08 ` Albert Cahalan
2004-08-17 1:54 ` James Courtier-Dutton
2004-08-17 2:03 ` Lee Revell
2004-08-17 20:52 ` George Anzinger
2004-08-17 6:56 ` Tim Schmielau
2004-08-17 20:07 ` john stultz
2004-08-17 20:13 ` [RFC] New timeofday implementation proposal john stultz
2004-08-17 20:58 ` [RFC] New timeofday code john stultz
2004-09-01 23:16 ` [RFC] New timeofday implementation proposal Christoph Lameter
2004-08-16 23:24 ` boot time, process start time, and NOW time Albert Cahalan
2004-08-17 19:00 ` john stultz
2004-08-17 17:41 ` Albert Cahalan
2004-08-17 20:58 ` john stultz
2004-08-17 20:25 ` [PATCH] " Tim Schmielau
2004-08-17 22:24 ` George Anzinger
2004-08-17 22:37 ` john stultz
2004-08-17 23:07 ` Tim Schmielau
2004-08-18 0:11 ` john stultz
2004-08-17 22:19 ` Albert Cahalan
2004-08-18 1:09 ` john stultz
2004-08-17 22:45 ` Albert Cahalan
2004-08-18 7:42 ` Tim Schmielau
2004-08-19 19:15 ` Petri Kaukasoina
2004-08-26 11:04 ` Andrew Morton
2004-08-26 12:07 ` Tim Schmielau
2004-08-30 23:00 ` Tim Schmielau
2004-08-30 23:38 ` john stultz
2004-08-31 0:37 ` Albert Cahalan [this message]
2004-08-31 0:49 ` Tim Schmielau
2004-08-31 0:45 ` Tim Schmielau
2004-08-31 1:23 ` john stultz
2004-08-31 1:34 ` john stultz
2004-08-31 6:07 ` Tim Schmielau
2004-08-31 19:27 ` George Anzinger
2004-08-31 20:56 ` john stultz
2004-08-31 21:10 ` David Ford
2004-09-02 20:39 ` George Anzinger
2004-09-01 19:14 ` OGAWA Hirofumi
2004-09-02 20:58 ` George Anzinger
2004-09-02 21:38 ` OGAWA Hirofumi
2004-09-03 0:59 ` George Anzinger
2004-09-03 3:35 ` OGAWA Hirofumi
2004-09-03 7:31 ` George Anzinger
2004-09-03 7:51 ` Tim Schmielau
2004-09-03 7:15 ` Tim Schmielau
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=1093912654.434.7022.camel@cube \
--to=albert@users.sf.net \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=david+powerix@blue-labs.org \
--cc=george@mvista.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=johnstul@us.ibm.com \
--cc=kaukasoi@elektroni.ee.tut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.george@ens.fr \
--cc=tim@physik3.uni-rostock.de \
--cc=voland@dmz.com.pl \
/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