Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Christian Suder <csuder@cisco.com>
To: "Grant Grundler" <grundler@dsl2.external.hp.com>
Cc: palinux@alaskatech.org, plaven@bigpond.net.au,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] bogomips?
Date: Sun, 13 Jan 2002 02:12:09 -0800	[thread overview]
Message-ID: <20020113021209.55bad2ea.csuder@cisco.com> (raw)
In-Reply-To: <20020112224306.C73ED482A@dsl2.external.hp.com>


http://www.linuxdoc.org/HOWTO/mini/BogoMips.html

For those who believe BogoMips matter..... ;-)

	Christian 


On Sat, 12 Jan 2002 15:43:06 -0700
"Grant Grundler" <grundler@dsl2.external.hp.com> wrote:

> Tom wrote:
> > As a rough guess, my 715/100 feels like a Pentium chip of roughly
twice> > the speed, while my C180 feels like a P2 of roughly twice the
speed. Don't> > know if the bogomips back that up, but that's the way they
feel.> 
> I've heard that from a bunch of people and seems like a good rule of
thumb.> 
> Someone once told me: "bogomips is just a dick waving contest".
> (apologies to any female readers who are offended).
> But that statement accurately  sums up how useful bogomips
> is for comparing perf.
> 
> grant
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2002-01-13 10:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-12 11:10 [parisc-linux] bogomips? Peter Lavender
2002-01-12 11:35 ` kenneth westelinck
2002-01-12 15:16   ` Michael S.Zick
2002-01-12 16:36 ` Randolph Chung
2002-01-12 17:00 ` Tom
2002-01-12 22:43   ` Grant Grundler
2002-01-13  8:53     ` kenneth westelinck
2002-01-13 10:12     ` Christian Suder [this message]
2002-01-13 11:25       ` Jochen Friedrich
2002-01-13 15:48       ` Michael S.Zick
2002-01-13 15:52         ` Matthew Wilcox
2002-01-13 16:08           ` Alan Cox
2002-01-13 15:53       ` Michael S.Zick

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=20020113021209.55bad2ea.csuder@cisco.com \
    --to=csuder@cisco.com \
    --cc=grundler@dsl2.external.hp.com \
    --cc=palinux@alaskatech.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=plaven@bigpond.net.au \
    /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