From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc [IPv6:2001:4d88:1ffa:82:880:aa0:9009:64ae]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 758052007D3 for ; Tue, 26 Mar 2013 13:02:24 -0700 (PDT) Received: from pfeifer by Chamillionaire.breakpoint.cc with local (Exim 4.72) (envelope-from ) id 1UKa4X-000555-E8; Tue, 26 Mar 2013 21:02:17 +0100 Date: Tue, 26 Mar 2013 21:02:16 +0100 From: Hagen Paul Pfeifer To: "Scheffenegger, Richard" Message-ID: <20130326200216.GB9410@virgo.local> References: <51408BF4.7090304@cisco.com> <201303261825.47601.mirja.kuehlewind@ikr.uni-stuttgart.de> <012C3117EDDB3C4781FD802A8C27DD4F24ACFA86@SACEXCMBX02-PRD.hq.netapp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <012C3117EDDB3C4781FD802A8C27DD4F24ACFA86@SACEXCMBX02-PRD.hq.netapp.com> X-Key-Id: 98350C22 X-Key-Fingerprint: 490F 557B 6C48 6D7E 5706 2EA2 4A22 8D45 9835 0C22 X-GPG-Key: gpg --recv-keys --keyserver wwwkeys.eu.pgp.net 98350C22 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: bloat , "aqm@ietf.org" , "tsvwg@ietf.org" Subject: Re: [Bloat] [tsvwg] [aqm] how much of a problem is buffer bloat today? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Mar 2013 20:02:24 -0000 * Scheffenegger, Richard | 2013-03-26 17:49:49 [+0000]: >TCP measures RTT; > >one could create a global histogram of all measured RTTs by TCP (whenever a >valid measurement is taken), and export that with "netstat -sp tcp"... Of >course, vastly different paths would be gobbled up together, but when >investigating specific paths, that should be good enough as a high level >starting point. For Linux tcp-probe[1] is your friend. The last colum is the smoothed round trip time. The port filter is optional and can be 0 to disable filtering. Not sure if Linux Distribution ship this module by default. But via tcp-probe you get accurate per-path rtt statistics without any effort (just a few CPU cycles). Hagen [1] http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe