From: Andrew Johnson <anj@aps.anl.gov>
To: "Justin (Gus) Hurwitz" <ghurwitz@dyndns.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: How fast should a bogomip be
Date: Wed, 11 Jul 2001 14:42:06 -0500 [thread overview]
Message-ID: <3B4CAC0E.2D08B233@aps.anl.gov> (raw)
In-Reply-To: Pine.LNX.3.95.1010711084748.21073D-100000@november.bhjjh.erols.com
"Justin (Gus) Hurwitz" wrote:
>
> I've seen numbers that indicate on 6xx series processors bogomips is
> usually about 2/3 the processor speed- so about 66.6 for a 100Mhz
> processor. I hope this is accurate, because that's what I'm getting.
When running with cache that sounds right from my very limited experience.
> But, about what should I expect for a 6xx (603e) 100Mhz processor running
> without cache? I've been trying to disable cache so I can continue
> development until the kernel supports propper allocation of non-cacheable
> memory (on a 603e with broken memory controller). When I run the kernel
> with code changes that *should* disable the cache the bootup process does
> feel marginally slower, and bogomips goes down a whopping .64 (from 66.56
> to 65.92). It then crashes with a segfault in kupdated (when in _wake_up).
> And I've been scratching my head trying to figure out a) whether the
> caches are actually disabled b) what causes that segfault, and c) how the
> two are related.
I can't help with the crash except to suggest that your patch isn't doing
what you think, and it certainly isn't disabling your cache. Could the
segfault be related to the the broken memory controller?
I was porting to a 200 MHz MPC8240 (ppc603ek?) board and initially had the
wrong code in head.S, such that the cache was not being enabled. The
BogoMIPS rating was then about 9.5; with the cache properly enabled I now
get 133.2 (~200*2/3). I suspect that the difference is a measurement of
the relative speed of the cache RAM compared to the main RAM - a factor of
13, which certainly seems in the right ballpark.
- Andrew
--
The world is such a cheerful place when viewed from upside-down
It makes a rise of every fall, a smile of every frown
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-11 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 12:58 How fast should a bogomip be Justin (Gus) Hurwitz
2001-07-11 19:42 ` Andrew Johnson [this message]
[not found] <Pine.LNX.3.95.1010711084748.21073D-100000@november.bhjjh.e rols.com>
2001-07-11 20:30 ` Jerry Van Baren
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=3B4CAC0E.2D08B233@aps.anl.gov \
--to=anj@aps.anl.gov \
--cc=ghurwitz@dyndns.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).