From: Andrew Derrick Balsa <andrebalsa@altern.org>
To: linux-kernel@vger.rutgers.edu
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"C. Scott Ananian" <cananian@lesser-magoo.lcs.mit.edu>,
Colin Plumb <colin@nyx.net>,
Rafael Reilova <rreilova@ececs.uc.edu>
Subject: [PATCH] 2.0.34: new time.c code
Date: Sun, 12 Jul 1998 12:27:52 +0200 [thread overview]
Message-ID: <98071212534804.00441@lw2l.bnc.interdrome.fr> (raw)
Hello,
Well, Scott having released his 2.1.10x code for "public consumption", here is a
2.0.34 version of the new time.c. Here is a summary of the new features:
- Gettimeofday() is now twice as fast. Takes on average 420 ns on my Cyrix
6x86MX 166MHz chip, whereas the original code took > 1 us. This provides a neat
boost for code that calls gettimeofday() very often. Note that on very fast
machines one may now get non-unique timestamps. This may or may not be a
problem, testing needed.
- Is not affected by TSC stopping/slowing down. Works on all CPUs without need
of a workaround. Works with APM.
- drift and jitter-free calibration of the TSC (the joystick driver, for one,
could use this calibration data).
- The code is shorter and more elegant than the present implementation.
- Shows CPU MHz at boot time. Precision is better than 0.01%.
- Allows for a very simple implementation of NTP time adjustments. Colin Plumb
is working on code for that. Note that the new code does _not_ break or affect
in any way the present NTP code. It will just make it easier for future NTP
implementations.
- Extremely robust. I have been testing it for 45 days now without any problems.
The 2.0.34 version differs very slightly from the 2.1.10x implementation in the
way the TSC is calibrated, in order to get > 5x better precision.
Note that neither the 2.0.34 version nor the 2.1.10x version have been tested
on SMP machines. Could somebody with an SMP box test this, please?
Cheers,
---------------------
Andrew D. Balsa
andrebalsa@altern.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
reply other threads:[~1998-07-12 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=98071212534804.00441@lw2l.bnc.interdrome.fr \
--to=andrebalsa@altern.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cananian@lesser-magoo.lcs.mit.edu \
--cc=colin@nyx.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=rreilova@ececs.uc.edu \
/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®