From owner-freebsd-current Sat Sep 5 00:41:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26503 for freebsd-current-outgoing; Sat, 5 Sep 1998 00:41:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26487 for ; Sat, 5 Sep 1998 00:41:04 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA11203; Sat, 5 Sep 1998 09:33:10 +0200 (CEST) To: Terry Lambert cc: mike@smith.net.au (Mike Smith), bde@zeta.org.au, caj@lfn.org, freebsd-current@FreeBSD.ORG Subject: Re: bzero bandwidth computation In-reply-to: Your message of "Sat, 05 Sep 1998 07:07:47 -0000." <199809050707.AAA29484@usr08.primenet.com> Date: Sat, 05 Sep 1998 09:33:10 +0200 Message-ID: <11201.904980790@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199809050707.AAA29484@usr08.primenet.com>, Terry Lambert writes: >> The current set of symptoms *seem* to be related to cycle-counter >> related interpolation being off because either the tick rate is erratic >> or the CPU speed is non-constant. It's looking like we can't rely on >> the cycle counter for accurate timing - this will be an issue with >> desktops as PC98 and PC99 systems start to become common too. 8( > >What does the cycle counter do in a HLT'ed CPU? count. -- 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