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
| ||
|
Date: Sun, 21 May 2017 13:38:04 -0400 (EDT) From: David Miller <davem@...emloft.net> To: mlichvar@...hat.com Cc: netdev@...r.kernel.org, richardcochran@...il.com, willemb@...gle.com Subject: Re: [PATCH v6 net-next 0/7] Extend socket timestamping API From: Miroslav Lichvar <mlichvar@...hat.com> Date: Fri, 19 May 2017 17:52:34 +0200 > This patchset adds new options to the timestamping API that will be > useful for NTP implementations and possibly other applications. > > The first patch specifies a timestamp filter for NTP packets. The second > patch updates drivers that can timestamp all packets, or need to list > the filter as unsupported. There is no attempt to add the support to the > phyter driver. > > The third patch adds two helper functions working with NAPI ID, which is > needed by the next patch. The fourth patch adds a new option to get a > new control message with the L2 length and interface index for incoming > packets with hardware timestamps. > > The fifth patch fixes documentation on number of non-zero fields in > scm_timestamping and warns about false software timestamps when > SO_TIMESTAMP(NS) is combined with SCM_TIMESTAMPING. > > The sixth patch adds a new option to request both software and hardware > timestamps for outgoing packets. The seventh patch updates drivers that > assumed software timestamping cannot be used together with hardware > timestamping. > > The patches have been tested on x86_64 machines with igb and e1000e > drivers. Series applied, thanks.
Powered by blists - more mailing lists