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: <CAF=yD-K=XDboSqVwqxLh1rjbgW5oCCa-yYs3zoTx-9O_7jmQoA@mail.gmail.com> Date: Tue, 16 May 2017 18:31:36 -0400 From: Willem de Bruijn <willemdebruijn.kernel@...il.com> To: Miroslav Lichvar <mlichvar@...hat.com> Cc: Network Development <netdev@...r.kernel.org>, Richard Cochran <richardcochran@...il.com>, Willem de Bruijn <willemb@...gle.com> Subject: Re: [PATCH v3 net-next 6/7] net: allow simultaneous SW and HW transmit timestamping On Tue, May 16, 2017 at 8:44 AM, Miroslav Lichvar <mlichvar@...hat.com> wrote: > Add SOF_TIMESTAMPING_OPT_TX_SWHW option to allow an outgoing packet to > be looped to the socket's error queue with a software timestamp even > when a hardware transmit timestamp is expected to be provided by the > driver. > > Applications using this option will receive two separate messages from > the error queue, one with a software timestamp and the other with a > hardware timestamp. As the hardware timestamp is saved to the shared skb > info, which may happen before the first message with software timestamp > is received by the application, the hardware timestamp is copied to the > SCM_TIMESTAMPING control message only when the skb has no software > timestamp or it is an incoming packet. > > While changing sw_tx_timestamp(), inline it in skb_tx_timestamp() as > there are no other users. > > CC: Richard Cochran <richardcochran@...il.com> > CC: Willem de Bruijn <willemb@...gle.com> > Signed-off-by: Miroslav Lichvar <mlichvar@...hat.com> Acked-by: Willem de Bruijn <willemb@...gle.com>
Powered by blists - more mailing lists