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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 4 Dec 2020 18:10:29 -0800 From: Jakub Kicinski <kuba@...nel.org> To: Vladimir Oltean <olteanv@...il.com> Cc: Saeed Mahameed <saeed@...nel.org>, "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org, Eran Ben Elisha <eranbe@...dia.com>, Tariq Toukan <tariqt@...dia.com>, Richard Cochran <richardcochran@...il.com>, Vladimir Oltean <vladimir.oltean@....com>, Willem de Bruijn <willemdebruijn.kernel@...il.com> Subject: Re: [net-next V2 08/15] net/mlx5e: Add TX PTP port object support On Sat, 5 Dec 2020 03:49:27 +0200 Vladimir Oltean wrote: > So there you go, it just says "the reference plane marking the boundary > between the PTP node and the network". So it depends on how you draw the > borders. I cannot seem to find any more precise definition. Ah, you made me go search :) I was referring to what's now section 90 of IEEE 802.3-2018. > Regardless of the layer at which the timestamp is taken, it is the > jitter that matters more than the reduced path delay. The latter is just > a side effect.
Powered by blists - more mailing lists