From: Eugene Surovegin <ebs@ebshome.net>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Wall clock accuracy
Date: Tue, 9 Aug 2005 09:41:25 -0700 [thread overview]
Message-ID: <20050809164125.GC22053@gate.ebshome.net> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B859416@ismail.innsys.innovsys.com>
On Tue, Aug 09, 2005 at 10:23:19AM -0500, Rune Torgersen wrote:
> Hi
>
> I have discovered that the accuracy of the wallclock (xtime) on ppc is
> not very good.
> I am running a custom telco board based on a 8266, and the main busclock
> is derived off of a T1 reference clock.
> I was noticing a huge number of logentries fron OpenNTPD about
> adjustiing the clock, so I started to check.
> The drift of the walltime was a little over 7 seconds in 15 hours (7
> seconds slow) (equals about 130us per s)
Hmm, if I'm correct this clock drift (130ppm) should be handled easily
by NTPD without stepping clock but with slewing. This is why NTPD
exists in the first place, so I don't see any reason to change
the kernel.
It's not small drift (I usually have clock accuracy within +-50ppm),
but still is much less than maximum 1024ppm NTPD can deal with.
Maybe it's an OpenNTPD problem? I use original NTPD (ntp.org) which
handles such drifts quite well.
--
Eugene
next prev parent reply other threads:[~2005-08-09 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 15:23 Wall clock accuracy Rune Torgersen
2005-08-09 16:41 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 16:57 Rune Torgersen
2005-08-09 16:59 ` Eugene Surovegin
2005-08-09 17:02 ` Eugene Surovegin
2005-08-09 17:04 Rune Torgersen
2005-08-09 17:20 ` Eugene Surovegin
2005-08-09 18:21 Rune Torgersen
2005-08-09 18:34 ` Eugene Surovegin
2005-08-09 18:52 Rune Torgersen
2005-08-09 18:56 ` Eugene Surovegin
2005-08-09 19:11 Rune Torgersen
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=20050809164125.GC22053@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=runet@innovsys.com \
/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;
as well as URLs for NNTP newsgroup(s).