linux-mips
[Top] [All Lists]

Re: BogoMIPS

To: Stuart Longland <stuartl@longlandclan.hopto.org>
Subject: Re: BogoMIPS
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 13 Apr 2005 13:47:12 +0100
Cc: Greg Weeks <greg.weeks@timesys.com>, linux-mips@linux-mips.org
In-reply-to: <425C9DBF.6090807@longlandclan.hopto.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <425BDCE4.6070708@timesys.com> <425C9DBF.6090807@longlandclan.hopto.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Wed, Apr 13, 2005 at 02:19:11PM +1000, Stuart Longland wrote:

> Probably, because it's no longer relevant these days.  It doesn't say
> anything special.

Nonsense.  It's just not printed to the screen by default.

> Interestingly, my IP28 still shows the BogoMIPS reading in /proc/cpuinfo:
> >stuartl@indigo ~ $ uname -a
> >Linux indigo 2.6.10-mipscvs-20050115-ip28 #2 Sun Apr 3 08:24:18 EST 2005 

Because you're running a vintage kernel.  The 0 BogoMIPS bug was
introduced by this CVS change:

  revision 1.54
  date: 2005/02/21 21:34:24;  author: ralf;  state: Exp;  lines: +2 -2
  On multiprocessor systems the BogoMIPS for each CPU was reported was
  the value for the last CPU having calibrated it's delay loop.

Only the value shown in /proc/cpuinfo on UP kernel was affected, so the
effect should be purely psychologic - I know what negative impact low
BogoMIPS may have on some people ;-)

  Ralf

<Prev in Thread] Current Thread [Next in Thread>