netdev - [PATCH net-next 0/5] PF_PACKET timestamping updates

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-next>] [day] [month] [year] [list]

Date:	Tue, 23 Apr 2013 12:39:27 +0200
From:	Daniel Borkmann <dborkman@...hat.com>
To:	davem@...emloft.net
Cc:	netdev@...r.kernel.org, willemb@...gle.com, Paul.Chavent@...ra.fr,
	richardcochran@...il.com
Subject: [PATCH net-next 0/5] PF_PACKET timestamping updates

This is a joint effort with Willem to bring optional i) tx hw/sw
timestamping into PF_PACKET, that was reported by Paul Chavent,
and ii) to expose the type of timestamp to the user, which is in
the current situation not possible to distinguish with the RX_RING
and TX_RING API (but distinguishable through the normal timestamping
API), reported by Richard Cochran. This set is based on top of
``packet: account statistics only in tpacket_stats_u''. Related
discussion can be found in: http://patchwork.ozlabs.org/patch/238125/

Daniel Borkmann (4):
  packet: enable hardware tx timestamping on tpacket ring
  packet: minor: convert status bits into shifting format
  packet: if hw/sw ts enabled in rx/tx ring, report which ts we got
  packet: doc: update timestamping part

Willem de Bruijn (1):
  packet: tx timestamping on tpacket ring

 Documentation/networking/packet_mmap.txt | 41 ++++++++++++---
 include/uapi/linux/if_packet.h           | 27 ++++++----
 net/core/skbuff.c                        | 12 ++---
 net/packet/af_packet.c                   | 87 ++++++++++++++++++++++++--------
 4 files changed, 122 insertions(+), 45 deletions(-)

-- 
1.7.11.7

--
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