From: Elizabeth Barham <soggytrousers@yahoo.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: tas@mindspring.com (Timothy A. Seufert),
langausd@fachschaft.informatik.uni-stuttgart.de (Siggi Langauf),
debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: "Cache Profiler" ? (was: No cache control on ppc??)
Date: 13 Jan 2002 02:06:45 -0600 [thread overview]
Message-ID: <877kqmvfmy.fsf@yahoo.com> (raw)
In-Reply-To: "Albert D. Cahalan"'s message of "Sun, 13 Jan 2002 01:51:58 -0500 (EST)"
Hi,
I recently installed a NewerTech Maxpowr G3 L2-Cache - which is a G3
on a board that fits into one of the L2's ram banks on my Starmax
3000/160. I was ecstatic that the bogomips increased by 187%
(199.47). Recently, though, I heard of someone installing a JoeBoard
into his StarMax 5000 and his bogomips being around 800. He mentioned
something about a "Cache Profiler". It seems that BootX is somehow
able to tell the kernel that there is a G3 in the cache and speed is
increased greatly.
The CPU on the StarMax 3000/160 motherboard itself (what originally
came with it) is a PPC 603e. /proc/cpuinfo shows a 750 - which is good
but the bogomips are nowhere near what this person reported. I do not
use BootX for I prefer booting straight into Linux with Quik. Does
anyone know anymore about this and if it's possible to increase
performance more by somehow making the G3 quicker?
Thank you,
Elizabeth
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-13 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0201121753510.11140-100000@darkwing.informatik.uni-stuttgart.de>
2002-01-12 21:39 ` No cache control on ppc?? Albert D. Cahalan
2002-01-13 5:36 ` Timothy A. Seufert
2002-01-13 6:51 ` Albert D. Cahalan
2002-01-13 8:06 ` Elizabeth Barham [this message]
2002-01-13 19:36 ` "Cache Profiler" ? (was: No cache control on ppc??) Benjamin Herrenschmidt
2002-01-15 9:17 ` Elizabeth Barham
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=877kqmvfmy.fsf@yahoo.com \
--to=soggytrousers@yahoo.com \
--cc=acahalan@cs.uml.edu \
--cc=debian-powerpc@lists.debian.org \
--cc=langausd@fachschaft.informatik.uni-stuttgart.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.com \
/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.