Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!psuvm!dxb132
From: DXB132@psuvm.psu.edu
Newsgroups: comp.arch
Subject: Re: Real Time/Cache
Message-ID: <90331.001007DXB132@psuvm.psu.edu>
Date: 27 Nov 90 05:10:07 GMT
References: <11190@pt.cs.cmu.edu>
Organization: Penn State University
Lines: 8

Perhaps it would be better in many cases to forget about the cache, and
simply put some fast static RAM in the memory map, to be used for time-
critical routines and data storage. The not-so-critical routines would be
placed in relatively slow memory (presumably you are thinking about very
large chunks of software else a pure static RAM approach is simpler and
just as cheap. Of course my idea of very large is 8K or so :-))

-- Dan Babcock