Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1177 comp.os.linux:55932
Newsgroups: comp.os.386bsd.misc,comp.os.linux
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!spool.mu.edu!sgiblab!slxinc!jonb
From: jonb@specialix.com (Jon Brawn)
Subject: Re: FYI.. benchmarks on linux and 386bsd
Organization: Specialix Inc.
Date: Fri, 8 Oct 1993 00:57:54 GMT
Message-ID: <CEK00J.LwA@specialix.com>
References: <2CB12A8D.17397@news.service.uci.edu> <28umsn$n4d@GRAPEVINE.LCS.MIT.EDU> <CGD.93Oct6131315@eden.CS.Berkeley.EDU>
Lines: 33
cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes:
>In article <28umsn$n4d@GRAPEVINE.LCS.MIT.EDU> metcalf@CATFISH.LCS.MIT.EDU (Chris Metcalf) writes:
>>Please note that "HZ" on Linux is 100, not 60, unlike most other common
>>Unix systems (SunOS, Ultrix, *BSD, etc.). Since 5217.4 / 8695.7 is
>>*exactly* 60/100, it's clear that the time taken under Linux was exactly
>>the same as the time taken under 386BSD. Note also that the "Dhampstone"
>>results were identical.
>hello?
>on *BSD, HZ is 100, and has been for a long time. (This includes {386,
>Free,Net}BSD).
>on SunOS, it's 60, for "compatibility reasons" or something like that.
>on Ultrix, it appears to be something like either 100 on some
>machines, or 256 on others (they've removed the #define, and
>replaced it with an entry in a cpu configuration table, or so it
>would seem).
>but for {386,Free,Net}BSD, you're definitely wrong, hz is 100,
>and always has been.
If it means anything, SCO Unix is HZ=100 too.
>chris
>--
>chris g. demetriou cgd@cs.berkeley.edu
> smarter than your average clam.