All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@gnudd.com>
To: nvbolhuis@aimvalley.nl
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: too few bogoMips on MPC8313E-RDB ?
Date: Wed, 26 Nov 2008 11:20:42 +0100	[thread overview]
Message-ID: <20081126102042.GA11397@mail.gnudd.com> (raw)
In-Reply-To: <492D1CA5.2090007@aimvalley.nl>

> This is what a linux-2.6.x reports (for the MPC8313E running at 333 MHz):
> Calibrating delay loop... 83.20 BogoMIPS (lpj=166400)
> 
> Which can't be correct.
> 
> A MPC870 (running at 133 mhz) has ~ 131.07 BogoMIPS

Actaully, one-instruction-per-clock leads to BogoMIPS = MHz.

Your "loop per jiffies" value shows you make 332800 instructions per
jiffy (a loop is two instructions: increment and jump).

So most liker your timer tick runs at 1000 Hz but Linux is thinking
it's at 250Hz (332800 * 250 = 83.20 millions).

> Of course it's only a benchmark figure.

No, it's not a benchmark figure. It's the metric by which udelay() is
calculated. So your udelays (and mdelays) will be 4 times shorter than
required, and some hardware may be misbehaving as a result.

Hope this help
/alessandro, who however is not runing a powerPC these times

  reply	other threads:[~2008-11-26 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26  9:53 too few bogoMips on MPC8313E-RDB ? Norbert van Bolhuis
2008-11-26 10:20 ` Alessandro Rubini [this message]
2008-11-26 14:20   ` Norbert van Bolhuis
2008-11-26 14:37     ` Leon Woestenberg
2008-11-26 14:41     ` Geert Uytterhoeven
2008-11-26 15:58     ` Dominik Bozek
2008-11-26 16:09       ` Norbert van Bolhuis
2008-11-26 17:05         ` Gabriel Paubert

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=20081126102042.GA11397@mail.gnudd.com \
    --to=rubini@gnudd.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=nvbolhuis@aimvalley.nl \
    /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.