netdev - Re: [PATCH net-next] dp83640: Adjust ptp event timestamps

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Jul 2014 19:41:49 +0200
From:	Richard Cochran <richardcochran@...il.com>
To:	Stefan Sørensen 
	<stefan.sorensen@...ctralink.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] dp83640: Adjust ptp event timestamps

On Wed, Jul 09, 2014 at 12:22:23PM +0200, Stefan Sørensen wrote:
> From the dp86340 Software Development Guide:
>   Event timestamp values should be adjusted by 3*reference clock period +
>   11 ns = 35 ns to compensate for input path and synchronization delays.
> 
> So subtract 35ns from event timestamps.

I have avoided adding this kind of thing into drivers because I think
people will want to make the correction in the delayAsymmetry field of
their user space stack. After all, this is exactly what that value is
supposed to cover.

Some parts have fixed delays (or at least they claim to) and some have
variable delays that can depend on link speed or other factors. So my
gut feeling tells me to be consistent and leave all such corrections
out, because in that way the end user will not have to research
whether a particular driver is "pre-correcting" or not.

Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html