netdev - [Question]: Details on TCP

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

Date:	Thu, 12 Mar 2015 10:58:38 -0700
From:	Martin Lau <kafai@...com>
To:	<tcpinst-wg@....edu>
CC:	rapier <rapier@....edu>, Eric Dumazet <eric.dumazet@...il.com>,
	Yuchung Cheng <ycheng@...gle.com>,
	netdev <netdev@...r.kernel.org>, <kernel-team@...com>
Subject: [Question]: Details on TCP_INFO extension

Old Title: [Tcpinst-wg] Welcome to the TCP Instrumentation List

On Thu, Feb 19, 2015 at 05:20:47PM -0500, rapier wrote:
> There should be two sets of instruments. Operational and diagnostic. The 
> operation instruments will be be used to extend TCP_INFO and will always 
> be available. Google will be providing a patch for upstream with 8 
> instruments in this category. The diagnostic instruments will be enabled 
> by the user on an as needed basis. These data from these instruments 
> will be stored in a separate structure that is referenced by a pointer 
> in the socket or some other mechanism. The ability to only enable a 
> subset of these instruments should be a design goal.
Can Google share which 8 fields will be added to TCP_INFO?

Thanks,
--Martin
--
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