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]
Date:	Thu, 21 May 2015 23:25:41 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	mleitner@...hat.com, edumazet@...gle.com, netdev@...r.kernel.org,
	ycheng@...gle.com, mattmathis@...gle.com, cgallek@...gle.com,
	kafai@...com, rapier@....edu
Subject: Re: [PATCH net-next] tcp: add tcpi_segs_in and tcpi_segs_out to
 tcp_info

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Wed, 20 May 2015 16:35:41 -0700

> From: Marcelo Ricardo Leitner <mleitner@...hat.com>
> 
> This patch tracks the total number of inbound and outbound segments on a
> TCP socket. One may use this number to have an idea on connection
> quality when compared against the retransmissions.
> 
> RFC4898 named these : tcpEStatsPerfSegsIn and tcpEStatsPerfSegsOut
> 
> These are a 32bit field each and can be fetched both from TCP_INFO
> getsockopt() if one has a handle on a TCP socket, or from inet_diag
> netlink facility (iproute2/ss patch will follow)
> 
> Note that tp->segs_out was placed near tp->snd_nxt for good data
> locality and minimal performance impact, while tp->segs_in was placed
> near tp->bytes_received for the same reason.
> 
> Join work with Eric Dumazet.
> 
> Note that received SYN are accounted on the listener, but sent SYNACK 
> are not accounted.
> 
> Signed-off-by: Marcelo Ricardo Leitner <mleitner@...hat.com>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>

Applied to net-next, thanks.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ