From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [144.76.141.112]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id B79CD21F1D2 for ; Mon, 2 Dec 2013 10:20:48 -0800 (PST) X-Virus-Scanned: amavisd-new at example.com Sender: toke@toke.dk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toke.dk; s=201310; t=1386008409; bh=Y5wUJy3+5J9aZM6fbCc72x2lqW+z+Xwqh1vQRd/OX2Y=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=vxp+MD8eL3KlV0fd1LWEnSK5Y++TwQLm+yBL4ufN/0baOJeHS7tyQiAApWjl63WyK 3fz7gPGVW42mDcsE0Pz+lpXuWXiXZCn1D3rtYcziTxpKRoR4qp861A4Z8jvR6WzQnt a03lPH7+2DGLi9I64PU4X4p0+bcWYdqxp5GqDAdc= Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 4B7F2E877; Mon, 2 Dec 2013 18:20:55 +0000 (GMT) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Rick Jones Subject: Re: One-way delay measurement for netperf-wrapper References: <87zjoojr5u.fsf@toke.dk> <87mwknk0hw.fsf@toke.dk> <529CCD6B.8000805@hp.com> Date: Mon, 02 Dec 2013 18:20:52 +0000 In-Reply-To: <529CCD6B.8000805@hp.com> (Rick Jones's message of "Mon, 02 Dec 2013 10:11:55 -0800") Message-ID: <87bo0z15dn.fsf@toke.dk> Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Cc: "bloat-devel@lists.bufferbloat.net" X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 18:20:49 -0000 --=-=-= Content-Type: text/plain Rick Jones writes: > Those TCP timestamps are generated (iirc) when TCP transmits the data, > not when the application presents the data to TCP. Not a deal breaker > necessarily, but something to keep in mind. Yeah, I was counting on that, actually. But I get your point: it's measuring two different things. I did not have the other use case in mind (application layer to application layer) until Lars mentioned it. I suppose doing both would be worthwhile, and probably some of the time-keeping logic can be reused. Still leaves the question of whether it's possible to get to the TCP timestamps short of sniffing the packets, though... Anyone knows? -Toke --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJSnM+EAAoJEENeEGz1+utPZYYH/0EfLEk0W1yyNoIU3p0HqMJG nsst2co3+eJNYOH2jeuKiZCCBvCix6iBOVU4wp2ZC8GJ7Ro0nuAUmEwD794Y6OUW lWXazi8mTmUzR2z8Yvhh7FfVsMDeN27xvDr6jkV7/F5dZcGLm/RFEttWI6RacRkF JU3GiOJeiG9vQQgGUqUYN/V6N59j2Yb7ujM8kI+HEldlnjYwHB5wKs3AHRAIYF6L sZGLje6D8hK+izP04RSgAhFKvVm71mkPntZytfS3AWg+3J6n6u2+GxlQbMvyePYp 3M8ai1DEoiOxD0f9Vde6/WuCb/xYyOibGdpudokQ8QrI1L7q+rWYdf4jtyYOqKo= =I8J2 -----END PGP SIGNATURE----- --=-=-=--