From owner-freebsd-arch Fri Oct 26 14:47:23 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 D6CC937B403; Fri, 26 Oct 2001 14:47:19 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9QLlJ838887; Fri, 26 Oct 2001 14:47:19 -0700 (PDT) (envelope-from dillon) Date: Fri, 26 Oct 2001 14:47:19 -0700 (PDT) From: Matthew Dillon Message-Id: <200110262147.f9QLlJ838887@apollo.backplane.com> To: John Baldwin Cc: 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 phrase 'no freaking way' comes to mind. :> :> You guys are outsmarting yourselves. Seconds, ok. That's it. Nothing :> else. The *VAST* majority of programs only need seconds, it would be :> utterly stupid to require that they mess around with some weird fixed :> point quantity when all they want is seconds, no matter how supposedly :> 'simple' that messing around is (i.e. '>> 64' is not acceptable). :> :> -Matt : :Umm. Dude, this is for the kernel's internal representations. We can massage :it in libc or in the kernel before it gets to userland. We do have to maintain :compatibility. Slow down and think about this for a second. : :-- : :John Baldwin -- http://www.FreeBSD.org/~jhb/ 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message