From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <chromatix99@gmail.com>
Received: from mail-bw0-f43.google.com (mail-bw0-f43.google.com
	[209.85.214.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client CN "smtp.gmail.com",
	Issuer "Google Internet Authority" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 0F7C1201146
	for <bloat-devel@lists.bufferbloat.net>;
	Wed, 21 Sep 2011 19:24:20 -0700 (PDT)
Received: by bkas6 with SMTP id s6so3283218bka.16
	for <bloat-devel@lists.bufferbloat.net>;
	Wed, 21 Sep 2011 19:24:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=subject:mime-version:content-type:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to:x-mailer;
	bh=nikMg23RIY2jbxexOxphPLeHjgzqwbTDcm3VVoXwHWQ=;
	b=XaBNQIMSDKO44qSYGBmKXdfN3RkTnCaoE7vVlsA5VZ+uOBjV32dyJQK2MMoLp8fw+v
	CiHkNQlpMpT72NWgtbUkAZhD2QlQgTq9D2ERZQuTvcs2B3GSFOHAi+x0WH+DaiJ9o8ll
	dBiVu0HdncFxdmynKKs7Upa8Vcb2GFhzSVHlI=
Received: by 10.204.154.199 with SMTP id p7mr986324bkw.151.1316658258996;
	Wed, 21 Sep 2011 19:24:18 -0700 (PDT)
Received: from [192.168.239.42] (xdsl-83-150-84-172.nebulazone.fi.
	[83.150.84.172])
	by mx.google.com with ESMTPS id d1sm6709674bku.1.2011.09.21.19.24.16
	(version=TLSv1/SSLv3 cipher=OTHER);
	Wed, 21 Sep 2011 19:24:17 -0700 (PDT)
Subject: Re: Preliminary results of using GPS to look for clock skew
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <20110922021137.GB21302@thyrsus.com>
Date: Thu, 22 Sep 2011 05:24:15 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D61AB68F-2055-4D1D-A71E-3C1F0AFD6BB1@gmail.com>
References: <20110921230205.2275820C2E5@snark.thyrsus.com>
	<CAA93jw6cdO9ou8JpnRtQw51jHtcuBC5J41Xg3iu6bRPs3MsVdA@mail.gmail.com>
	<20110922021137.GB21302@thyrsus.com>
To: esr@thyrsus.com
X-Mailer: Apple Mail (2.1084)
Cc: bloat-devel@lists.bufferbloat.net, Eric Raymond <esr@snark.thyrsus.com>,
	Hal Murray <hmurray@megapathdsl.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" <bloat-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat-devel>,
	<mailto:bloat-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat-devel>
List-Post: <mailto:bloat-devel@lists.bufferbloat.net>
List-Help: <mailto:bloat-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat-devel>,
	<mailto:bloat-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 22 Sep 2011 02:24:21 -0000


On 22 Sep, 2011, at 5:11 am, Eric Raymond wrote:

>> 2) ReRun all tests under load (example: netperf -l 3600 -H =
the_router)
>=20
> I'll do this, for completeness, but I predict it's not going to make
> any measurable difference.  The indications so far are that neither of
> the means of time delivery I have available to check are compute-bound
> or disk-I/O bound at any point in their delivery chains. =20
>=20
> So I think they're just going to shrug off any load short of
> machine-thrashing-its-guts-out.  But part of the point of what I'm
> doing is that soon we'll have the test tools to know for *sure* that's
> true.

When the *network* is loaded, the latency to the NTP server changes.  =
That is likely to confuse ntpd - it certainly did when I lived on an =
analogue modem.

 - Jonathan Morton