From: "Mark Chambers" <mwchambers@citlink.net>
To: "Gerrit Van de Velde" <gvd@denayer.wenk.be>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Motorola 5200 MIPS
Date: Mon, 3 May 2004 10:39:20 -0400 [thread overview]
Message-ID: <002101c4311c$6ca7d440$0301a8c0@chuck2> (raw)
In-Reply-To: 4095ED18.50605@denayer.wenk.be
> Don't know, but you're not comparing the right numbers anyway. Try
> running a Dhrystone benchmark. It reported something around 500 MIPS.
I suspect 500MIPS is probably pretty close, judging by some of the tests
I've run.
OK, I know I'm anal-retentive, but I can't just accept "it has 'bogo' in the
name, so therefore it means nothing." We've run linux on several 8xx family
parts and the bogomips closely tracked the expected performance of 1
instruction/clock. Now all of a sudden it doesn't mean anything? So I
tracked it down, and the bogoMIPS calculation all boils down to a "bdnz"
instruction (on a PPC). So on pipelined processors branches are the worst
case scenario. I think it boils down to taking 2 processor cycles/bdnz
instruction. So, it's a worst case scenario, but then again 760MIPS is a
best case scenario, assuming you can always feed two instructions into the
CPU every clock cycle (and never have to branch!). Not going to happen, so
you've got to assume you can reasonably expect 1-point-something times the
processor clock.
Mark Chambers
Microfirst, Inc.
P.S. I'm a fan of Motorola processors, hope I didn't sound too ugly. What
would the world be like if Bill had chosen the 68000???
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-03 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 22:25 Motorola 5200 MIPS Mark Chambers
2004-04-30 22:46 ` Gary Thomas
2004-05-03 6:56 ` Gerrit Van de Velde
2004-05-03 14:39 ` Mark Chambers [this message]
2004-05-03 15:32 ` Wolfgang Denk
2004-05-03 17:33 ` Mark Chambers
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='002101c4311c$6ca7d440$0301a8c0@chuck2' \
--to=mwchambers@citlink.net \
--cc=gvd@denayer.wenk.be \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).