From: john stultz <johnstul@us.ibm.com>
To: Alexander Gordeev <lasaine@lvk.cs.msu.su>
Cc: linux-kernel@vger.kernel.org, linuxpps@ml.enneenne.com,
"Nikita V. Youshchenko" <yoush@cs.msu.su>,
stas@lvk.cs.msu.su, Rodolfo Giometti <giometti@enneenne.com>
Subject: Re: [PATCHv2 0/6] pps: time synchronization over LPT
Date: Mon, 8 Mar 2010 19:25:07 -0800 [thread overview]
Message-ID: <1f1b08da1003081925p61a810e4v96be56640287d61@mail.gmail.com> (raw)
In-Reply-To: <cover.1267008049.git.lasaine@lvk.cs.msu.su>
On Wed, Feb 24, 2010 at 4:28 AM, Alexander Gordeev
<lasaine@lvk.cs.msu.su> wrote:
> This patchset is tested against the vanilla 2.6.32.9 kernel. But we are
> actually using it on 2.6.31.12-rt20 rt-preempt kernel most of the time.
> Also there is a version which should be applied on top of LinuxPPS out
> of tree patches (i.e. all clients and low-level irq timestamps stuff).
> Those who are interested in other versions of the patchset can find
> them in my git repository:
> http://lvk.cs.msu.su/~lasaine/timesync/linux-2.6-timesync.git
>
> There is one problem however: hardpps() works bad when used on top
> of 2.6.33-rc* with CONFIG_NO_HZ enabled. The reason for this is commit
> a092ff0f90cae22b2ac8028ecd2c6f6c1a9e4601. Without it hardpps() is able
> to sync to 1us precision in about 10 seconds. With it
Uh. Not sure I see right off why the logarithmic time accumulation
would give you troubles. Its actually there to try to fix a couple of
NTP issues that cropped up when the accumulation interval was pushed
out to 2HZ with CONFIG_NO_HZ.
Do you have any extra insight here as to whats going on with your
code? The only thing I could guess would be second_overflow() is
happening closer to the actual overflow, but maybe less regularly? But
again, I'm not sure how this would be drastically different then
before with the 2HZ accumulation period.
thanks
-john
next prev parent reply other threads:[~2010-03-09 3:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 12:28 Alexander Gordeev
2010-02-24 12:28 ` [PATCHv2 1/6] ntp: add hardpps implementation Alexander Gordeev
2010-03-01 8:14 ` Rodolfo Giometti
2010-03-01 10:43 ` Alexander Gordeev
2010-02-24 12:28 ` [PATCHv2 2/6] pps: unify timestamp gathering Alexander Gordeev
2010-03-01 8:18 ` Rodolfo Giometti
2010-02-24 12:28 ` [PATCHv2 3/6] pps: capture MONOTONIC_RAW timestamps as well Alexander Gordeev
2010-03-01 8:19 ` Rodolfo Giometti
2010-02-24 12:28 ` [PATCHv2 4/6] pps: add kernel consumer support Alexander Gordeev
2010-03-01 8:29 ` Rodolfo Giometti
2010-03-01 10:48 ` Alexander Gordeev
2010-02-24 12:28 ` [PATCHv2 5/6] pps: add parallel port PPS signal generator Alexander Gordeev
2010-03-01 8:38 ` Rodolfo Giometti
2010-03-01 10:51 ` Alexander Gordeev
2010-02-24 12:28 ` [PATCHv2 6/6] pps: add parallel port PPS client Alexander Gordeev
2010-03-01 8:42 ` Rodolfo Giometti
2010-03-09 3:25 ` john stultz [this message]
2010-03-22 20:42 ` [PATCHv2 0/6] pps: time synchronization over LPT Alexander Gordeev
2010-03-22 21:01 ` john stultz
2010-03-22 21:37 ` Alexander Gordeev
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=1f1b08da1003081925p61a810e4v96be56640287d61@mail.gmail.com \
--to=johnstul@us.ibm.com \
--cc=giometti@enneenne.com \
--cc=lasaine@lvk.cs.msu.su \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxpps@ml.enneenne.com \
--cc=stas@lvk.cs.msu.su \
--cc=yoush@cs.msu.su \
/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®