From: Peter Zijlstra <peterz@infradead.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3 1/4] Add correlated clocksource deriving system time from an auxiliary clocksource
Date: Fri, 4 Sep 2015 17:10:21 +0200 [thread overview]
Message-ID: <20150904151021.GF18489@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1509041438520.15006@nanos>
On Fri, Sep 04, 2015 at 03:02:19PM +0200, Thomas Gleixner wrote:
> > For example, supply the ART value as an argument and, in the case of
> > the realtime clock, keep a short history of clock changes. It would
>
> It's not only clock realtime which is affected by those.
>
> > fail in cases where there are a lot of calls to adjtimex(),
>
> That has nothing to do with lots of adjtimex calls. The kernel does a
> slow correction of the conversion values itself to avoid time jumping
> around.
I think what they're getting at is asking if there's a rate limit to
time adjustments, without that, saving the last n transition points will
still not cover any given length of history.
So what I think they're looking for; is given an upper bound on the DSP
delaying its data, come up with a fixed minimal amount of transitions
points we must store to cover the history.
next prev parent reply other threads:[~2015-09-04 15:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 18:52 [Intel-wired-lan] [PATCH v3 0/4] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2015-08-21 18:52 ` [Intel-wired-lan] [PATCH v3 1/4] Add correlated clocksource deriving system time from an auxiliary clocksource Christopher S. Hall
2015-08-22 20:17 ` Thomas Gleixner
2015-09-03 23:20 ` Hall, Christopher S
2015-09-04 8:11 ` Richard Cochran
2015-09-04 14:28 ` Peter Zijlstra
2015-09-04 21:12 ` Hall, Christopher S
2015-09-04 13:02 ` Thomas Gleixner
2015-09-04 15:10 ` Peter Zijlstra [this message]
2015-09-04 15:17 ` Richard Cochran
2015-09-04 15:41 ` Peter Zijlstra
2015-09-04 16:35 ` Thomas Gleixner
2015-09-04 21:01 ` Hall, Christopher S
2015-09-05 8:46 ` Thomas Gleixner
2015-09-05 10:04 ` Ingo Molnar
2015-09-04 15:32 ` Richard Cochran
2015-09-04 21:50 ` John Stultz
2015-08-21 18:52 ` [Intel-wired-lan] [PATCH v3 2/4] Added ART correlated clocksource and ART CPU feature Christopher S. Hall
2015-08-22 20:26 ` Thomas Gleixner
2015-08-21 18:52 ` [Intel-wired-lan] [PATCH v3 3/4] Add support for driver cross-timestamp to PTP_SYS_OFFSET ioctl Christopher S. Hall
2015-08-22 20:33 ` Thomas Gleixner
2015-08-22 21:17 ` Richard Cochran
2015-08-23 8:15 ` Thomas Gleixner
2015-08-23 11:25 ` Richard Cochran
2015-08-24 20:16 ` Hall, Christopher S
2015-08-25 7:31 ` Richard Cochran
2015-08-21 18:52 ` [Intel-wired-lan] [PATCH v3 4/4] Enabling hardware supported PTP system/device crosstimestamping Christopher S. Hall
2015-08-22 20:46 ` Thomas Gleixner
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=20150904151021.GF18489@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=intel-wired-lan@osuosl.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