Re: [Question]: Details on TCP_INFO extension

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2015-03-12 at 10:58 -0700, Martin Lau wrote:
> Old Title:  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
> --

CC Eric Salo, who is working on this topic.

Note that I upstreamed yesterday support for an unified socket cookie.

http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=33cf7c90fe2f97afb1cadaa0cfb782cb9d1b9ee2



_______________________________________________
Tcpinst-wg mailing list
Tcpinst-wg@xxxxxxx
https://lists.psc.edu/mailman/listinfo/tcpinst-wg

To UNSUBSCRIBE visit https://lists.psc.edu/mailman/unsubscribe/tcpinst-wg




[Index of Archives]     [Linux Kernel]     [Networking Development]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]