All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: BogoMIPS no longer supported on PowerPC?
Date: Wed, 23 Aug 2006 09:51:38 -0500	[thread overview]
Message-ID: <20060823145138.GH614@pb15.lixom.net> (raw)
In-Reply-To: <4879B0C6C249214CBE7AB04453F84E4D0FC20C@zch01exm20.fsl.freescale.net>

On Wed, Aug 23, 2006 at 06:55:26PM +0800, Li Yang-r58472 wrote:
> Ok, I rephrase my question as is it no longer needed?  Sometimes people
> may use this value as a rough estimation of CPU performance.  There are
> people even maintained a list of bogoMIPS of most CPUs.  Maybe it is
> still needed for some legacy reasons.  I'm not very sure.  :)   At leave
> we need to inform people who do look at this magic number and find it
> amazingly low.

Bogomips has never had anything to do with performance on PPC, it's just
a number that's based on the decrementer frequency. For processors with
external/fixed decrementer clock, it will not vary between different
processors in a meaningful way.

Every now and then someone will ask "why does my PPC box have such low
bogomips, is it really that much slower than my PC?". Removing all output
would certainly help avoid that confusion.

For reference, my G5 here has 66.56 bogomips, which corresponds well to
the 33MHz decrementer clock it uses.


-Olof

  reply	other threads:[~2006-08-23 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 10:25 BogoMIPS no longer supported on PowerPC? Li Yang-r58472
2006-08-23 10:37 ` Johannes Berg
2006-08-23 10:55   ` Li Yang-r58472
2006-08-23 14:51     ` Olof Johansson [this message]
2006-08-23 16:47       ` Li Yang
2006-08-23 18:06       ` Linas Vepstas
2006-08-23 16:32   ` Tim Bird
2006-08-23 16:46     ` Li Yang
2006-08-23 16:50     ` Olaf Hering

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=20060823145138.GH614@pb15.lixom.net \
    --to=olof@lixom.net \
    --cc=LeoLi@freescale.com \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.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 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.