From owner-freebsd-current@FreeBSD.ORG  Wed Dec 19 13:04:45 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id B9018571;
 Wed, 19 Dec 2012 13:04:45 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 3F7AB8FC12;
 Wed, 19 Dec 2012 13:04:45 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
 by phk.freebsd.dk (Postfix) with ESMTP id C90E189EAF;
 Wed, 19 Dec 2012 13:04:43 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id qBJD4gQR016440;
 Wed, 19 Dec 2012 13:04:42 GMT (envelope-from phk@phk.freebsd.dk)
To: Bruce Evans <brde@optusnet.com.au>
Subject: Re: API explosion (Re: [RFC/RFT] calloutng)
In-reply-to: <20121219221518.E1082@besplex.bde.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <50CF88B9.6040004@FreeBSD.org>
 <20121218173643.GA94266@onelab2.iet.unipi.it> <50D0B00D.8090002@FreeBSD.org>
 <50D0E42B.6030605@FreeBSD.org> <20121218225823.GA96962@onelab2.iet.unipi.it>
 <1355873265.1198.183.camel@revolution.hippie.lan>
 <14604.1355910848@critter.freebsd.dk>
 <CACYV=-Eg542iHm9KfujPvCzZrA4TqepEBVA8RzT1YOHnCgfJnA@mail.gmail.com>
 <15882.1355914308@critter.freebsd.dk> <20121219221518.E1082@besplex.bde.org>
Date: Wed, 19 Dec 2012 13:04:42 +0000
Message-ID: <16439.1355922282@critter.freebsd.dk>
Cc: Davide Italiano <davide@FreeBSD.org>,
 Ian Lepore <freebsd@damnhippie.dyndns.org>, Alexander Motin <mav@FreeBSD.org>,
 phk@onelab2.iet.unipi.it, freebsd-current <freebsd-current@FreeBSD.org>,
 "freebsd-arch@freebsd.org" <freebsd-arch@FreeBSD.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 13:04:45 -0000

--------
In message <20121219221518.E1082@besplex.bde.org>, Bruce Evans writes:

>> With this format you can specify callouts 68 years into the future
>> with quarter nanosecond resolution, and you can trivially and
>> efficiently compare dur_t's with
>> 	if (d1 < d2)
>
>This would make a better general format than timevals, timespecs and
>of course bintimes :-).

Except that for absolute timescales, we're running out of the 32 bits
integer part.

Bintimes is a necessary superset of the 32.32 which tries to work
around the necessary but missing int96_t or int128_t[1].

Poul-Henning


[1] A good addition to C would be a general multi-word integer type
where you could ask for any int%d_t or uint%d_t you cared for, and
have the compiler DTRT.  In difference from using a multiword-library,
this would still give these types their natural integer behaviour.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.