From owner-freebsd-arch Fri Oct 26 14:50:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 42C8337B406; Fri, 26 Oct 2001 14:50:23 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9QLoMB38937; Fri, 26 Oct 2001 14:50:22 -0700 (PDT) (envelope-from dillon) Date: Fri, 26 Oct 2001 14:50:22 -0700 (PDT) From: Matthew Dillon Message-Id: <200110262150.f9QLoMB38937@apollo.backplane.com> To: John Baldwin , Poul-Henning Kamp , arch@FreeBSD.ORG, Peter Wemm , Bakul Shah Subject: Re: 64 bit times revisited.. References: 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 : 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. : -Matt 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 Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message