From: Marcus Sundberg <marcus@cendio.se>
To: Seungdong Lee <sdlee@da-san.com>
Cc: Dan Malek <dan@netx4.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8240 BogoMIPS
Date: 22 May 2000 11:34:57 +0200 [thread overview]
Message-ID: <vevh07dj26.fsf@lipta.cendio.se> (raw)
In-Reply-To: Seungdong Lee's message of "Mon, 22 May 2000 11:38:29 +0900"
Seungdong Lee <sdlee@da-san.com> writes:
> Marcus Sundberg wrote:
> > I'm not very familiar with 82x0 processors, but doesn't 8240 use a
> > 603-core? When I worked with a 603ev running at 200 MHz I got
> > something like 133 BogoMIPS, so then the above value would be correct.
> >
>
> Good information.
> But, why it is 133 BogoMIPS?
Because that's what a 200 MHz PowerPC 603 gives you.
Checking the BogoMIPS howto will show you one report of a 603,
running at 100 MHz and giving 66 BogoMIPS, which is at par with
our results.
> I still think that the correct value is 400.
Unless you have tried other 603-based sytems you have no reason to
think so. I repeat my statement from the previous post:
> > The BogoMIPS can be used for rough sanity-checks when comparing
> > processors with identical cores and different clocks. For anything
> > else it's completely useless.
//Marcus
--
-------------------------------+-----------------------------------
Marcus Sundberg | Phone: +46 707 452062
Embedded Systems Consultant | Email: marcus@cendio.se
Cendio Systems AB | http://www.cendio.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-22 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-20 7:28 8240 BogoMIPS Seungdong Lee
2000-05-20 17:36 ` Dan Malek
2000-05-20 20:14 ` Marcus Sundberg
2000-05-22 2:38 ` Seungdong Lee
2000-05-22 9:34 ` Marcus Sundberg [this message]
2000-05-22 9:54 ` Seungdong Lee
2000-05-22 10:50 ` Geir Frode Raanes
2000-05-22 11:19 ` Seungdong Lee
2000-05-26 7:45 ` Seungdong Lee
2000-05-22 2:29 ` Seungdong Lee
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=vevh07dj26.fsf@lipta.cendio.se \
--to=marcus@cendio.se \
--cc=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sdlee@da-san.com \
/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.