netdev - Re: [net-next, v3, 1/2] enetc: mark TX timestamp type per skb

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]

Message-ID: <d9021cef-873d-6238-6201-698850444bdc@gmail.com>
Date:   Mon, 12 Apr 2021 21:59:53 +0300
From:   Claudiu Manoil <claudiu.manoil@...il.com>
To:     Yangbo Lu <yangbo.lu@....com>, netdev@...r.kernel.org
Cc:     "David S . Miller" <davem@...emloft.net>,
        Richard Cochran <richardcochran@...il.com>,
        Claudiu Manoil <claudiu.manoil@....com>,
        Jakub Kicinski <kuba@...nel.org>,
        Vladimir Oltean <vladimir.oltean@....com>,
        Russell King <linux@...linux.org.uk>
Subject: Re: [net-next, v3, 1/2] enetc: mark TX timestamp type per skb

On 12.04.2021 12:03, Yangbo Lu wrote:
> Mark TX timestamp type per skb on skb->cb[0], instead of
> global variable for all skbs. This is a preparation for
> one step timestamp support.
> 
> For one-step timestamping enablement, there will be both
> one-step and two-step PTP messages to transfer. And a skb
> queue is needed for one-step PTP messages making sure
> start to send current message only after the last one
> completed on hardware. (ENETC single-step register has to
> be dynamically configured per message.) So, marking TX
> timestamp type per skb is required.
> 
> Signed-off-by: Yangbo Lu <yangbo.lu@....com>

Reviewed-by: Claudiu Manoil <claudiu.manoil@....com>