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 B336E21F228 for ; Thu, 28 Nov 2013 10:52:00 -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=1385664660; bh=+KpZYonh2p+ll18TK0fBqzfeQ1NpZx1hzndXCzCKxao=; h=From:To:Subject:Date; b=YvjPpR1my5HWzg8Qg2vMzFuaOYVIpKn2PhWx8xcam5rhH6kTf763aLFdVegL9cmZ7 LvtdmQfq0NP54pbyP8f5LEHXroH3O8DttsMxuQsKyDH4NrLLFMvQfaT/Opm9wjRoK7 XlNAfFK+JAhIBM3trIKF4kXHInSf5RUkZNsqo8/8= Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 1D70ADC77; Thu, 28 Nov 2013 18:51:44 +0000 (GMT) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: bloat-devel@lists.bufferbloat.net Subject: One-way delay measurement for netperf-wrapper Date: Thu, 28 Nov 2013 18:51:41 +0000 Message-ID: <87zjoojr5u.fsf@toke.dk> Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" 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: Thu, 28 Nov 2013 18:52:01 -0000 --=-=-= Content-Type: text/plain So I've been thinking about adding one-way delay measurement to netperf-wrapper, but thought I'd solicit some input on how best to do that. The obvious way would be to parse owamp[1] output, but since that relies on clock synchronisation (and is another dependency), perhaps it might be worth looking at other approaches. The people at LINCS seem to have had some success with passive measurements of induced queueing delay based on TCP timestamps[2]; would adding something like that to (e.g.) netperf be worthwhile? And is it possible (as in, is there an API to get to the timestamp values) for TCP? Other ideas? -Toke [1] http://www.infres.enst.fr/~drossi/index.php?n=Dataset.BufferbloatMethodology [2] http://www.enst.fr/~drossi/dataset/bufferbloat-methodology --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJSl5C9AAoJEENeEGz1+utP3HwH/iSL9Cpnd2wq1OZEIeOtjyCu Vh25srzIcr/1OfyQq4jShlDEXLewciMQkhTwm8UmlgKF9lXbRFYJ0x9CnJAavyXZ BbIdNyyDB7Ecr+FcCMVChUCwPr+RtBLyVbF9az6+Z/GBJwoYPvLoTKXIzp0H/KYZ mk5u9Gc023OumLVZOPV9DPEFg44rFwcwLA7sIMfaSJDdYRwznYfTGslHDrEOzG0d +HKYN6lUVL+9KImcIMKe+7VTBq46f+jvDVO38KLNYAK+jZ3tvRGNC7CrrS8XAOuC gY225RO5q+3uEKpp6pifNu0ySxgcn8t1KMU0oOQSRyqzmwwmgrLCwEkx15xZEqk= =799N -----END PGP SIGNATURE----- --=-=-=--