From: Ralf Baechle <ralf@linux-mips.org>
To: Stuart Longland <stuartl@longlandclan.hopto.org>
Cc: Greg Weeks <greg.weeks@timesys.com>, linux-mips@linux-mips.org
Subject: Re: BogoMIPS
Date: Wed, 13 Apr 2005 13:47:12 +0100 [thread overview]
Message-ID: <20050413124712.GF5253@linux-mips.org> (raw)
In-Reply-To: <425C9DBF.6090807@longlandclan.hopto.org>
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
next prev parent reply other threads:[~2005-04-13 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 14:36 BogoMIPS Greg Weeks
2005-04-13 4:19 ` BogoMIPS Stuart Longland
2005-04-13 11:36 ` BogoMIPS Greg Weeks
2005-04-13 13:21 ` BogoMIPS Ralf Baechle
2005-04-13 12:47 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-06-17 14:28 bogomips Mike Shaver
1997-06-06 11:35 bogomips Mike Shaver
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=20050413124712.GF5253@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=greg.weeks@timesys.com \
--cc=linux-mips@linux-mips.org \
--cc=stuartl@longlandclan.hopto.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.