: Details on TCP_INFO extension
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
Old Title: [Tcpinst-wg] Welcome to the TCP Instrumentation List
Quoted 8 lines · rapier
There should be two sets of instruments. Operational and diagnostic. The operation instruments will be be used to extend
TCP_INFOand 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
Quoted 11 lines · Martin Lau
Old Title: [Tcpinst-wg] Welcome to the TCP Instrumentation List
Quoted 8 lines · rapier
There should be two sets of instruments. Operational and diagnostic. The operation instruments will be be used to extend
TCP_INFOand 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.
Quoted 5 lines
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.