diff mbox series

[RFC,V1,net-next,2/6] net: skbuff: Add a field to support time based transmission.

Message ID 555939002f1ca9d89b14f30b3579445e4fa628d9.1505719061.git.rcochran@linutronix.de
State RFC, archived
Delegated to: David Miller
Headers show
Series Time based packet transmission | expand

Commit Message

Richard Cochran Sept. 18, 2017, 7:41 a.m. UTC 
Signed-off-by: Richard Cochran <rcochran@linutronix.de>
---
 include/linux/skbuff.h | 2 ++
 1 file changed, 2 insertions(+)

Comments

Eric Dumazet Sept. 18, 2017, 3:14 p.m. UTC | #1 
On Mon, 2017-09-18 at 09:41 +0200, Richard Cochran wrote:
> Signed-off-by: Richard Cochran <rcochran@linutronix.de>
> ---
>  include/linux/skbuff.h | 2 ++
>  1 file changed, 2 insertions(+)

Why skb->tstamp can not be used ?

AFAIK, fact that it might be overwritten by packet captures should not hurt.
diff mbox series

Patch

diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 72299ef00061..bc7f7dcbb413 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -635,6 +635,7 @@  typedef unsigned char *sk_buff_data_t;
  *	@dst_pending_confirm: need to confirm neighbour
   *	@napi_id: id of the NAPI struct this skb came from
  *	@secmark: security marking
+ *	@transmit_time: desired future transmission time in nanoseconds
  *	@mark: Generic packet mark
  *	@vlan_proto: vlan encapsulation protocol
  *	@vlan_tci: vlan tag control information
@@ -804,6 +805,7 @@  struct sk_buff {
 #ifdef CONFIG_NETWORK_SECMARK
 	__u32		secmark;
 #endif
+	__u64			transmit_time;
 
 	union {
 		__u32		mark;