mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stock IA64 kernel on SGI Altix 350
Date: Fri, 4 Jun 2004 08:03:02 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0406040753300.7010@ppc970.osdl.org> (raw)
In-Reply-To: <20040604120925.GE20632@lug-owl.de>



On Fri, 4 Jun 2004, Jan-Benedict Glaw wrote:

> On Thu, 2004-06-03 22:09:06 +0200, Jan Kasprzak <kas@informatics.muni.cz>
> wrote in message <20040603200905.GA27701@fi.muni.cz>:
> [ia64 booting]
> > CPU 1: base freq=200.000MHz, ITC ratio=14/2, ITC freq=1400.000MHz+/--1ppm
> > Calibrating delay loop... 16.44 BogoMIPS
> 
> Hihi:) A ~ 55MHz VAX does nothing with about 15 BogoMIPS.

Yeah, the bogomips have become too bogus to even be useful these days.

Just as a clarification, "bogomips" is really "bogo-timing-events-per-
second-multiplied-by-two" (aka "bogotepsmbt").

The "timing event" used to be a "two-instruction loop", which is where the 
"multiplied-by-two" comes from: at that point the "bogotepsmbt" becomes 
the number of instructions per second, and that explains the "mips" part 
of the name.

But since it's really used for timing small delay loops, and since the
two-instruction loop wasn't very good at that (due to power-usage, SMT
issues, frequency changes, you name it), the implementations have sadly 
started to drift away from using instruction retire as the event they 
count, and start using a separate counter instead.

So 16.44 BogoMIPS these days really implies " ~8MHz timer frequency ".

The timer is a lot better from a technical standpoint, but it sure is a 
hell of a lot less entertaining than the original MIPS thing..

			Linus

  reply	other threads:[~2004-06-04 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 17:01 Jan Kasprzak
2004-06-03 17:30 ` Jesse Barnes
2004-06-03 20:09   ` Jan Kasprzak
2004-06-03 20:19     ` Jesse Barnes
2004-06-03 20:41       ` Jan Kasprzak
2004-06-04 12:09     ` Jan-Benedict Glaw
2004-06-04 15:03       ` Linus Torvalds [this message]
2004-06-03 17:34 ` Paul Jackson
     [not found] <962201031@toto.iv>
2004-06-04  3:59 ` Peter Chubb

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=Pine.LNX.4.58.0406040753300.7010@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®