| 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
| ||
|
Message-ID: <54F0A7DB.9070103@linn.co.uk> Date: Fri, 27 Feb 2015 17:22:35 +0000 From: Stathis Voukelatos <stathis.voukelatos@...n.co.uk> To: <linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>, <devicetree@...r.kernel.org> Subject: Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver Hi Richard, On 25/02/15 17:30, Richard Cochran wrote: >> I need some more time to study your other suggestions regarding the >> PHY timestamping framework. > > From my (limited) understanding of your HW device, I should think that > it will work. The PHY time stamping subsystem is not the most obvious > code in the world. Please feel free to ask if you have any questions. > To summarize (and confirm my understanding) your suggestion is for the sniffer to be configured to match PTP packets and (similarly to the dp83640) return the Message Type and Sequence Id fields that will allow them to be matched to an sk_buf that has been passed from the stack. Then the sk_buf can be timestamped using the sniffer timestamp. The H/W does have the capability to do that. However, in order to implement it there will be some architectural changes needed in the kernel. This module cannot really pretend to be a PHY. In the real world it sits between the MAC and the PHY. > Thanks, > Richard > Thanks, Stathis -- 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
Powered by blists - more mailing lists