Quoting Christoph Lameter :
On Thu, 23 Sep 2010, Christian Riesch wrote:
> > It implies clock tuning in userspace for a potential sub microsecond
> > accurate clock. The clock accuracy will be limited by user space
> > latencies and noise. You wont be able to disciplin
Alan Cox wrote:
It implies clock tuning in userspace for a potential sub microsecond
accurate clock. The clock accuracy will be limited by user space
latencies and noise. You wont be able to discipline the system clock
accurately.
Noise matters, latency doesn't.
Well put! That's why we need
Alan Cox wrote:
Please do not introduce useless additional layers for clock sync. Load
these ptp clocks like the other regular clock modules and make them sync
system time like any other clock.
I don't think you understand PTP. PTP has masters, a system can need to
be honouring multiple conflic
Alan Cox wrote:
The master node in a PTP network probably takes its time from a
precise external time source, like GPS. The GPS provides a 1 PPS
directly to the PTP clock hardware, which latches the PTP hardware
clock time on the PPS edge. This provides one sample as input to a
clock servo (in th
On Mon, Aug 23, 2010 at 10:08 PM, john stultz wrote:
> On Thu, 2010-08-19 at 07:55 +0200, Richard Cochran wrote:
>> On Wed, Aug 18, 2010 at 05:12:56PM -0700, john stultz wrote:
>> > Again, my knowledge in the networking stack is pretty limited. But it
>> > would seem that having an interface that
