Article View: comp.arch
Article #20492physical vs. virtual cache
From: Wm. E. Davidsen Jr
Date: Fri, 24 Mar 1989 13:19
Date: Fri, 24 Mar 1989 13:19
14 lines
928 bytes
928 bytes
Would someone like to describe the less obvious features of cache types
in terms of real estate, design problems, etc? I see lots of allusions
but damn few hard facts.
Unless you disagree with these, they've been mentioned many times:
virtual:
fast, no address translation needed
physical:
no need to flush on context switch
no aliasing problems
--
bill davidsen (wedu@crd.GE.COM)
{uunet | philabs}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me
Technical Details
Message-ID:
<13413@steinmetz.ge.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!itsgw!steinmetz!davidsenShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!itsgw!steinmetz!davidsen From: davidsen@steinmetz.ge.com (Wm. E. Davidsen Jr) Newsgroups: comp.arch Subject: physical vs. virtual cache Keywords: cache Message-ID: <13413@steinmetz.ge.com> Date: 24 Mar 89 13:19:38 GMT Reply-To: davidsen@crdos1.UUCP (bill davidsen) Distribution: na Organization: GE Corp. R & D, Schenectady,NY Lines: 14