Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!bionet!ucselx!crash!pnet01!lkoop
From: lkoop@pnet01.cts.com (Lamonte Koop)
Newsgroups: comp.sys.amiga
Subject: Re: Populous for all Amigas!
Message-ID: <5031@crash.cts.com>
Date: 14 Oct 90 09:36:01 GMT
Sender: root@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 24

zerkle@iris.ucdavis.edu (Dan Zerkle) writes:
>In article <32943@nigel.ee.udel.edu> lawsonse@vttcf.cc.vt.edu (Shannon Lawson) writes:

[much stuff deleted]
>
>The cache problem can be avoided on 68000 machines that have
>accellerators (A2500, GVP-enhanced, whatever) by using the 68000.  Some
>systems let you turn off the cache in their accellerators.
>Unfortunately, neither of these is an option in the A3000, which has
>only a 68030, and no option for turning off the caching.  In any case,
>turning off the cache results in reduced performance.

This is not a correct statement about the 68030.  Any 68030 or 68020 can have 
it's code and/or data caching inhibited through the setting of it's cache
control register (CACR) in said way.  However, it is a correct assessment taht
this degrades performance.  Noticable in a 32-bit environment, and if you
happen to be running in a 16-bit environment with the Instruction cache off,
it can be like moving through molasses.



UUCP: {hplabs!hp-sdd ucsd nosc}!crash!pnet01!lkoop
ARPA: crash!pnet01!lkoop@nosc.mil
INET: lkoop@pnet01.cts.com