From: Michael S.Zick <mszick@pflash.com>
To: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] bogomips?
Date: Sun, 13 Jan 2002 09:53:32 -0600 [thread overview]
Message-ID: <02011309533201.00878@localhost.localdomain> (raw)
In-Reply-To: <20020113021209.55bad2ea.csuder@cisco.com>
Oops,
I am once again exposed as a fool. Please ignore my earlier copy of this
message - I didn't read the full reference. The change from 1.0 * clock to
2.0 * clock is described in the reference.
Sorry folks,
Mike
On Sunday 13 January 2002 04:12 am, Christian Suder wrote:
> http://www.linuxdoc.org/HOWTO/mini/BogoMips.html
>
> For those who believe BogoMips matter..... ;-)
>
> Christian
>
Well, I would never claim that BogoMips is, in its self, useful for anything.
But since its code is closely related to the udelay code, which affects
scheduling and many drivers...
Once upon a time, both my Celeron and my P-II reported approximately 1.00 *
clock (same as above reference), then with some change of kernel version,
jumped to 2.00 * clock.
BUT, that might have been an intentional change in the routine, or...
No promises on this one: I sometimes keep old kernels, perhaps I can find the
"before and after" kernels where I noticed the change.
Mike
prev parent reply other threads:[~2002-01-13 15:56 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
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 [this message]
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=02011309533201.00878@localhost.localdomain \
--to=mszick@pflash.com \
--cc=parisc-linux@parisc-linux.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.