linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: "Stuart Adams" <sja@brightstareng.com>, <linuxppc-embedded@ozlabs.org>
Subject: Re: MPC5200 bogomips
Date: Thu, 27 Jan 2005 12:52:32 -0500	[thread overview]
Message-ID: <003501c50498$fb92f720$0301a8c0@chuck2> (raw)
In-Reply-To: 41F916ED.1070705@brightstareng.com


----- Original Message ----- 
From: "Stuart Adams" <sja@brightstareng.com>
To: <linuxppc-embedded@ozlabs.org>
Sent: Thursday, January 27, 2005 11:29 AM
Subject: MPC5200 bogomips


> 
>   We are only seeing 263.78 bogomips on a MPC5200 running
>   at 396 MHz.
> 
>   Doesn't this seem way to low ?? With a 603e core I'd expect
>   1 bogomip per MHz or better.
> 
>   The exact same kernel source running on an 8xx PPC gets about
>   1 bogomip per MHZ and my 745 CPU board does 2 bogomips
>   per MHz ... the bogomip calibration code is the same for all
>   PPC architectures so it seem like it should be an apples-to-apples
>   comparison.
> 
> -- Stuart
> 

Ha! You almost sound like you are quoting me from when I first
looked at bogomips on the 5200.  Here's the story:  If you drill
down to where bogomips are calculated you will see that it is
measuring the speed of a dbnz instruction.  The calculation assumes
2 clocks per dbnz.  So the 8xx comes out at 1 BogoMIP/MHz.  The
5200 takes 3 clocks/dbnz in this loop, so you get .67 BogoMIP/MHz.  
Not to worry, it's only one specific scenario.  Overall I've found the 
5200 to be about 1.5 MIPS/MHz compared to 8xx 1 MIPS/MHz.

Mark Chambers

      reply	other threads:[~2005-01-27 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 16:29 MPC5200 bogomips Stuart Adams
2005-01-27 17:52 ` Mark Chambers [this message]

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='003501c50498$fb92f720$0301a8c0@chuck2' \
    --to=markc@mail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sja@brightstareng.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 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).