From owner-freebsd-arch Fri Oct 26 15: 1:43 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 3AEF437B401; Fri, 26 Oct 2001 15:01:40 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9QM16M09135; Sat, 27 Oct 2001 00:01:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: John Baldwin , arch@FreeBSD.ORG, Peter Wemm , Bakul Shah Subject: Re: 64 bit times revisited.. In-Reply-To: Your message of "Fri, 26 Oct 2001 14:50:22 PDT." <200110262150.f9QLoMB38937@apollo.backplane.com> Date: Sat, 27 Oct 2001 00:01:06 +0200 Message-ID: <9133.1004133666@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200110262150.f9QLoMB38937@apollo.backplane.com>, Matthew Dillon wri tes: > >: The best kernel-internal time representnation is ticks, with a simple >: baseline cache mechanism to convert it to other formats (e.g. as >: required by NFS, UFS, userland, etc...). Nothing beats ticks... >: a binary fixed point format doesn't even come *close* to being better >: then straight ticks. >: > > Before this gets misinterpreted, the 'ticks' I am talking about is > not the kernel timer interrupt ticks... it's the high resolution cpu > or 825x ticks we get. e.g. frequency dependant on the timer we use. Matt, that is the mess Linux is fighting with. We have had a superior solution for years by now which even allows us to change timekeeping hardware on the fly as we find more suitable timebases. -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message