Re: firewire: CLOCK_MONOTONIC_RAW exposure

From: Clemens Ladisch
Date: Wed Jul 16 2014 - 10:16:45 EST


Peter Zijlstra wrote:
> On Wed, Jul 16, 2014 at 01:34:21PM +0200, Clemens Ladisch wrote:
>> Thomas Gleixner wrote:
>>> I wonder why firewire exposed CLOCK_MONOTONIC_RAW to user space.
>>>
>>> What's the purpose of that? CLOCK_MONOTONIC_RAW is the raw time based
>>> on the initial frequency setup of the clocksource. That can be quite
>>> off from the NTP corrected frequency which is exposed by
>>> CLOCK_MONOTONIC.
>>
>> The purpose is to get a stable clock, i.e., to avoid clock rate changes
>> caused by NTP corrections.
>
> That's maybe half an answer; what do you need that for?

According to the original report, "for applications which need to
synchronise with external timebases such as broadcast TV applications".
Such external clocks are not synchronous with any available clocksource,
so proper resampling requires that the (relative) rate of the two clocks
(sender and playback device) is measured accurately.

(I don't have numbers for the errors caused by NTP adjustments. Daniel?)


Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/