> Date: Fri, 22 May 1998 00:12:40 -0100
> From: "[ISO-8859-1] André Derrick Balsa" <andrebalsa@altern.org>
> To: Pavel Machek <pavel@atrey.karlin.mff.cuni.cz>
> Cc: linker@nightshade.ml.org, linux-kernel@vger.rutgers.edu
> Subject: Re: To Bogomips or not to Bogomips?
>
> Hi,
>
> Pavel Machek wrote:
> >
> > Hi!
> >
> > > > Please keep it. If someone wants to know MHz, get that userland
> > > > utility. But keep bogomips in kernel.
> > >
> > > Bogomips will still be reported every time at kernel boot time. If
> > > anybody wants to check it, just do "dmesg".
> >
> > No. dmesg overflows. It does on my machine pretty fast, it does on
> > production servers. You may not rely on dmesg.
>
> Oh come on!
>
> Do "cat /var/log/dmesg" if you can't rely on "dmesg" alone...
And what's wrong with /proc/cpuinfo?
$ cat /proc/cpuinfo
processor : 0
cpu : 686
model : 5
vendor_id : GenuineIntel
stepping : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
fpu : yes
fpu_exception : yes
cpuid : yes
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic 11 mtrr pge mca cmov 16 17 mmx 24
bogomips : 397.31
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu