From: Michael S.Zick <mszick@pflash.com>
To: "Peter Lavender" <plaven@bigpond.net.au>
Cc: "parisc" <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] bogomips?
Date: Sat, 12 Jan 2002 09:16:18 -0600 [thread overview]
Message-ID: <02011209161801.01008@localhost.localdomain> (raw)
In-Reply-To: <OE60SJBsBrwvvIfPvhi000088a7@hotmail.com>
Hmmm....
I don't know if this is the intended operation or not (probably a question
for the Linux tree dudes), but...
Kenneth's 486 reports at about 1/2 the clock speed (also notice the lack of a
cpu MHz line in the report).
This Celeron reports at about 2* the clock speed. (Kernel 2.4.17)
If memory (mine) serves, my P-II system reported at appox. bogomips == cpu
clock. I don't recall what my Pentium or 386 system reported and have never
had a 486.
I think I noticed the change in the relationship between bogomips and cpu
clock early in kernel 2.2.x (while I was running the P-II system) - perhaps
something has crept in from the Linux tree that is having this effect.
Mike
[mszick@localhost /proc]$ cat ./cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 6
model name : Celeron (Mendocino)
stepping : 5
cpu MHz : 467.737
cache size : 128 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov
pat pse36 mmx fxsr
bogomips : 930.61
[mszick@localhost /proc]$
On Saturday 12 January 2002 05:35 am, you wrote:
> Hmm, don't know.
>
> My little 486DX4 100MHz, 12MB RAM:
> /proc# cat ./cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 4
> model : 8
> model name : 486 DX/4
> stepping : 0
> fdiv_bug : no
> hlt_bug : no
> sep_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme
> bogomips : 49.66
>
> /proc#
>
>
> regards,
>
> Kenneth
>
> ----- Original Message -----
> From: "Peter Lavender" <plaven@bigpond.net.au>
> To: "parisc" <parisc-linux@parisc-linux.org>
> Sent: Saturday, January 12, 2002 12:10 PM
> Subject: [parisc-linux] bogomips?
>
> > Hi everyone,
> >
> > What's a 715/64 equate to in terms of intel arches?
> >
> > Here's my p90 with 48meg of ram:
> > Calibrating delay loop... 35.84 BogoMIPS
> >
> > and my 715/64 with 128 meg of ram:
> > Calibrating delay loop... 63.69 BogoMIPS
> >
> > Thanks,
> >
> > Pete
> >
> >
> > _______________________________________________
> > parisc-linux mailing list
> > parisc-linux@lists.parisc-linux.org
> > http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2002-01-12 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 11:10 [parisc-linux] bogomips? Peter Lavender
2002-01-12 11:35 ` kenneth westelinck
2002-01-12 15:16 ` Michael S.Zick [this message]
2002-01-12 16:36 ` Randolph Chung
2002-01-12 17:00 ` Tom
2002-01-12 22:43 ` Grant Grundler
2002-01-13 8:53 ` kenneth westelinck
2002-01-13 10:12 ` Christian Suder
2002-01-13 11:25 ` Jochen Friedrich
2002-01-13 15:48 ` Michael S.Zick
2002-01-13 15:52 ` Matthew Wilcox
2002-01-13 16:08 ` Alan Cox
2002-01-13 15:53 ` Michael S.Zick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02011209161801.01008@localhost.localdomain \
--to=mszick@pflash.com \
--cc=parisc-linux@parisc-linux.org \
--cc=plaven@bigpond.net.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.