🚀 go-pugleaf

In article <7711@watdaisy.UUCP> dneudoerffer@watdaisy.UUCP (Dave Neudoerffer) writes:
>I think we need some clarification on what cache we're talking about here.
>I agree with Henry that a process identification tag on addresses
>in the memory management translation cache (TLB) is a bonus and saves
>flushes of this cache.
>Also if a data cache is used between processor and memory management, 
>ie caching virtual addresses, then this tag may also be useful.  However,
>as Ben points out, you can get physical address aliasing if two
>processes are accessing the some memory page.
>However, if a data cache is put in the system after the memory management
>hardware, there is no aliasing problem since only physical addresses
>are being cached.  I beleive this last setup is the one found in most
>systems with a data cache.
>

Ah, but putting the cache AFTER the memory management hardware puts
the address translation in the critical path for ALL memory accesses,
whether the reference hits the cache or not.

Too bad if TLB lookup (or whatever) is more than an insignificant fraction
of cache access time.  It is easier to implement, though.  Of course,
if the processor is slow enough that time(TLB+cache) is still quick from
the processor's point of view, it doesn't matter.  Nobody would ever
want to buy a faster processor, would they? :-)

-- 
Eric Black   "Garbage In, Gospel Out"
UUCP:        {sun,pyramid,hplabs,amdcad}!chronon!eric
WELL:        eblack
BIX:         eblack