From owner-freebsd-stable@FreeBSD.ORG  Sun Jan 27 17:54:32 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 0F8EC731;
 Sun, 27 Jan 2013 17:54:32 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id ED622E1D;
 Sun, 27 Jan 2013 17:54:30 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA21632;
 Sun, 27 Jan 2013 19:54:29 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1TzWR3-000JYk-2d; Sun, 27 Jan 2013 19:54:29 +0200
Message-ID: <510569D3.2030000@FreeBSD.org>
Date: Sun, 27 Jan 2013 19:54:27 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130121 Thunderbird/17.0.2
MIME-Version: 1.0
To: Adrian Chadd <adrian@FreeBSD.org>
Subject: Re: time issues and ZFS
References: <E1TxFcr-0006dx-MX@kabab.cs.huji.ac.il>
 <1358780588.32417.414.camel@revolution.hippie.lan>
 <E1TxJP2-000DS8-DJ@kabab.cs.huji.ac.il>
 <1358783667.32417.434.camel@revolution.hippie.lan>
 <CAJ-Vmo=2Dmf4Lb-uoUQDrybyRSS=_bnV5KcNYGg5MnMxfhhu7w@mail.gmail.com>
 <E1TxYHa-0002yo-4Y@kabab.cs.huji.ac.il>
 <CAJ-VmomdQORjs55ooW55Rgg0i1M13PPtnmCPRrp__btEWQz=4g@mail.gmail.com>
 <E1TxaZv-0005fj-5m@kabab.cs.huji.ac.il>
 <CAJ-VmokQbZFGmmy=KkEmP+7a6DQRGhdgupqF4sNCGJYxvA-B0g@mail.gmail.com>
 <50FFFA8B.4040008@FreeBSD.org>
 <CAJ-Vmon7pT6=UJ5ppRO_3SWRw-QM9W2Bz1=ffq2ovjxHGyOUrA@mail.gmail.com>
 <5103ACAE.5060406@FreeBSD.org>
 <CAJ-VmokZV2g3+TFJAFNnJ1MD+igrLxN9fGd4267UmPJMWsX-aw@mail.gmail.com>
In-Reply-To: <CAJ-VmokZV2g3+TFJAFNnJ1MD+igrLxN9fGd4267UmPJMWsX-aw@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@FreeBSD.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 17:54:32 -0000

on 27/01/2013 19:27 Adrian Chadd said the following:
> On 26 January 2013 02:15, Andriy Gapon <avg@freebsd.org> wrote:
>> on 23/01/2013 18:20 Adrian Chadd said the following:
>>> It may be a quirk of an older 9.x, which is fixed in -HEAD. It may be
>>> a quirk of the older generation celeron hardware - in which case, we
>>> need to tell the user somehow..
>>
>> This is not software related at all.  It's the hardware feature (or its absence).
>> I wonder if your celerons report PBE feature.
> 
> What am I looking for?

PBE in dmesg

> And personally, requiring (much) more recent hardware to get
> sane/correct (btu inefficient) behaviour out of the timekeeping
> framework is a little .. suboptimal. :)

Well, I never knew about this issue before but I always assumed that the
reasonable behavior was the behavior.  And I never encountered any evidence to
the contrary.

-- 
Andriy Gapon