Date: Fri, 26 Oct 2001 14:47:19 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, arch@FreeBSD.ORG, Peter Wemm <peter@wemm.org>, Bakul Shah <bakul@bitblocks.com> Subject: Re: 64 bit times revisited.. Message-ID: <200110262147.f9QLlJ838887@apollo.backplane.com> References: <XFMail.011026143448.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:> 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 <jhb@FreeBSD.org> -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110262147.f9QLlJ838887>