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

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160402.211942.598210499165268433.davem@davemloft.net>
Date:	Sat, 02 Apr 2016 21:19:42 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	soheil.kdev@...il.com
Cc:	netdev@...r.kernel.org, willemb@...gle.com, edumazet@...gle.com,
	ycheng@...gle.com, ncardwell@...gle.com, kafai@...com,
	soheil@...gle.com
Subject: Re: [PATCH v2 net-next 0/8] add TX timestamping via cmsg

From: Soheil Hassas Yeganeh <soheil.kdev@...il.com>
Date: Fri,  1 Apr 2016 11:04:32 -0400

> From: Soheil Hassas Yeganeh <soheil@...gle.com>
> 
> 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.

Series applied, thanks.