Re: [PATCH v3 net-next 0/8] add TX timestamping via cmsg

[David Miller <davem@davemloft.net>]

From: Soheil Hassas Yeganeh <soheil.kdev@gmail.com>
Date: Sat,  2 Apr 2016 23:08:05 -0400

> This patch series aim at enabling TX timestamping via cmsg.
> 
> Currently, to occasionally sample TX timestamping on a socket,
> applications need to call setsockopt twice: first for enabling
> timestamps and then for disabling them. This is an unnecessary
> overhead. With cmsg, in contrast, applications can sample TX
> timestamps per sendmsg().
> 
> This patch series adds the code for processing SO_TIMESTAMPING
> for cmsg's of the SOL_SOCKET level, and adds the glue code for
> TCP, UDP, and RAW for both IPv4 and IPv6. This implementation
> supports overriding timestamp generation flags (i.e.,
> SOF_TIMESTAMPING_TX_*) but not timestamp reporting flags.
> Applications must still enable timestamp reporting via
> setsockopt to receive timestamps.
> 
> This series does not change existing timestamping behavior for
> applications that are using socket options.
> 
> I will follow up with another patch to enable timestamping for
> active TFO (client-side TCP Fast Open) and also setting packet
> mark via cmsgs.
 ...
> Changes in v2:
>         - Replace u32 with __u32 in the documentation.
> 
> Changes in v3:
> 	- Fix the broken build for L2TP (due to changes
> 	  in IPv6).

Series applied, thanks.