netdev - RE: [Intel-wired-lan] [PATCH v9 iwl-next 08/10] idpf: add Tx timestamp flows

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 for Android: free password hash cracker in your pocket

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

Message-ID: <SJ1PR11MB62975E4FB165D7BA025BBFE79BD22@SJ1PR11MB6297.namprd11.prod.outlook.com>
Date: Fri, 14 Mar 2025 20:24:08 +0000
From: "Salin, Samuel" <samuel.salin@...el.com>
To: "Olech, Milena" <milena.olech@...el.com>,
	"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Nguyen, Anthony L"
	<anthony.l.nguyen@...el.com>, "Kitszel, Przemyslaw"
	<przemyslaw.kitszel@...el.com>, "Olech, Milena" <milena.olech@...el.com>,
	"Hay, Joshua A" <joshua.a.hay@...el.com>
Subject: RE: [Intel-wired-lan] [PATCH v9 iwl-next 08/10] idpf: add Tx
 timestamp flows



> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of
> Milena Olech
> Sent: Thursday, March 13, 2025 11:04 AM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org; Nguyen, Anthony L
> <anthony.l.nguyen@...el.com>; Kitszel, Przemyslaw
> <przemyslaw.kitszel@...el.com>; Olech, Milena <milena.olech@...el.com>;
> Hay, Joshua A <joshua.a.hay@...el.com>
> Subject: [Intel-wired-lan] [PATCH v9 iwl-next 08/10] idpf: add Tx timestamp
> flows
> 
> Add functions to request Tx timestamp for the PTP packets, read the Tx
> timestamp when the completion tag for that packet is being received, extend
> the Tx timestamp value and set the supported timestamping modes.
> 
> Tx timestamp is requested for the PTP packets by setting a TSYN bit and index
> value in the Tx context descriptor. The driver assumption is that the Tx
> timestamp value is ready to be read when the completion tag is received. Then
> the driver schedules delayed work and the Tx timestamp value read is
> requested through virtchnl message. At the end, the Tx timestamp value is
> extended to 64-bit and provided back to the skb.
> 
> Co-developed-by: Josh Hay <joshua.a.hay@...el.com>
> Signed-off-by: Josh Hay <joshua.a.hay@...el.com>
> Signed-off-by: Milena Olech <milena.olech@...el.com>
> ---
> 2.31.1

Tested-by: Samuel Salin <Samuel.salin@...el.com>