From owner-freebsd-net@FreeBSD.ORG Thu Apr 30 21:07:16 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED2DDDBF for ; Thu, 30 Apr 2015 21:07:16 +0000 (UTC) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C1EF81D10 for ; Thu, 30 Apr 2015 21:07:16 +0000 (UTC) Received: from 82-69-116-12.dsl.in-addr.zen.co.uk ([82.69.116.12]:58432 helo=[172.16.33.1]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1Ynvfo-00045P-CL; Thu, 30 Apr 2015 17:07:09 -0400 From: "George Neville-Neil" To: "Karlis Laivins" Cc: "Eggert, Lars" , "freebsd-net@freebsd.org" , "grenville armitage" Subject: Re: Congestion Control Modification Date: Thu, 30 Apr 2015 22:06:58 +0100 Message-ID: <8D3AEF2A-1413-4C44-9E5C-66900847F18A@neville-neil.com> In-Reply-To: References: <5535945F.90504@swin.edu.au> <98E7D40A-EC37-413D-85CE-2A6012811E08@netapp.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.1r5084) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Apr 2015 21:07:17 -0000 If you want to run some experiments, though, you could look at running PTPd on 3 servers (master, and two slaves) which will get you decent synchronization among the three. Where decent is less than the typical RTT of a TCP packet on a 1Gbps LAN. Best, George On 30 Apr 2015, at 14:48, Karlis Laivins wrote: > Yes, you are correct, I meant to write "relative OWD". As David Hayes > put > it - "Relative OWD measurements are easier, and clock drift is not > usually > a problem over the time it takes to send and receive an ACK". > > Thank you for the correction! > > On Thu, Apr 30, 2015 at 4:19 PM, Eggert, Lars wrote: > >> On 2015-4-30, at 15:04, Karlis Laivins >> wrote: >>> I have yet to solve the issue of >>> how to get the One Way Delay for the ACK message (the time it takes >>> ACK >> to >>> arrive from receiver of the ACK'ed data sender) correctly. >> >> That won't work without synchronized clocks, which you can't really >> assume >> to be present. >> >> Lars