From owner-freebsd-current Fri Sep 4 04:42:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11741 for freebsd-current-outgoing; Fri, 4 Sep 1998 04:42:00 -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 EAA11721 for ; Fri, 4 Sep 1998 04:41:57 -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 NAA02799; Fri, 4 Sep 1998 13:36:15 +0200 (CEST) To: Bruce Evans cc: caj@lfn.org, freebsd-current@FreeBSD.ORG Subject: Re: bzero bandwidth computation In-reply-to: Your message of "Fri, 04 Sep 1998 21:32:47 +1000." <199809041132.VAA10135@godzilla.zeta.org.au> Date: Fri, 04 Sep 1998 13:36:15 +0200 Message-ID: <2797.904908975@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199809041132.VAA10135@godzilla.zeta.org.au>, Bruce Evans writes: >>>>From a boot -v on my Thinkpad 560E running -current >>>(GenuineIntel 166MMX pentium): >>> >>>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... > >That might have given a negative bandwidth :-). No, that would be unlikely. Many APM seem to power up with the CPU in a reduced speed mode, and then after a short time the crank it up to full speed. -- 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