Date: Fri, 04 Sep 1998 18:11:51 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Mike Smith <mike@smith.net.au> Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzero bandwidth computation Message-ID: <4436.904925511@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 04 Sep 1998 09:04:21 PDT." <199809041604.QAA03644@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199809041604.QAA03644@word.smith.net.au>, Mike Smith writes: >> >> >i586_bzero() bandwidth = 173130193 bytes/sec >> >> >bzero() bandwidth = 688705234 bytes/sec (!!!) >> >> > >> >> >Hrm, a bit fishy eh? >> >> >> >> APM strikes again I bet... Your CPU clock changed speed while it ran... >> > >> >Sounds like our clock code is totally screwed then. You have 12 >> >days... 8) >> >> Sounds like out clock code is now good enough to show you that APM >> has screwed you, as opposed to people asking you if your clock is >> set right because your emails tend to timewarp... > >8) I know my timezone is wrong. > >The problem here is that we're supposed to work on PC hardware. It >would be nice if we could count on it being designed for precision >timekeeping, but it looks like hardware vendors have other ideas. I agree, but we were more wrong before, we just wouldn't notice. I'm working on a scheme where we track the RTC without going to a 1/128Hz granularity, but it is non-trivial. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4436.904925511>