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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 26 Feb 2007 15:41:10 -0300 From: "Arnaldo Carvalho de Melo" <arnaldo.melo@...il.com> To: "Michael Faber" <faber@...informatik.rwth-aachen.de> Cc: netdev@...r.kernel.org Subject: Re: tcp_info struct On 2/26/07, Michael Faber <faber@...informatik.rwth-aachen.de> wrote: > Hi, > > i want to use the tcp_info struct to keep track of some tcp related > information. This works fine so far, however i'm wondering how to > interpret some of the values delivered. I would expect values like cwnd > and sst to be given out in packets regarding the source code. Can anyone > give me some hints in interpreting the tcp_info values as this option is > very poor documented and only documentation on how to fill the tcp_info > struct can be found. Rule #N: Use the current users as the documentation Use rule #N, by looking at the iproute2 source code, more specifically the ss source code 8) - Arnaldo - 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
Powered by blists - more mailing lists