Article View: comp.arch
Article #2247the meaning of "memory-locked" (was Re: How Caches Work)
From: Andrew Klossner
Date: Thu, 14 Sep 1989 19:44
Date: Thu, 14 Sep 1989 19:44
10 lines
1023 bytes
1023 bytes
"This idea is already in use by some MMU systems - it's called
uncacheable (or memory-locked) pages."
Would that it weren't. In the US, at least, the term "memory locked"
denotes a page that it not a candidate to be swapped out to backing
store.
-=- Andrew Klossner (uunet!tektronix!frip.WV.TEK!andrew) [UUCP]
(andrew%frip.wv.tek.com@relay.cs.net) [ARPA]
Technical Details
Message-ID:
<4550@orca.WV.TEK.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!zephyr.ens.tek.com!orca!frip!andrewReferences:
<21936@cup.portal.com> <1082@cernvax.UUCP> <16306@watdragon.waterloo.edu> <RANG.89Sep10184900@derby.cs.wisc.edu> <8399@boring.cwi.nl> <3989@phri.UUCP> <2569@taux01.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!zephyr.ens.tek.com!orca!frip!andrew From: andrew@frip.WV.TEK.COM (Andrew Klossner) Newsgroups: comp.arch Subject: the meaning of "memory-locked" (was Re: How Caches Work) Message-ID: <4550@orca.WV.TEK.COM> Date: 14 Sep 89 19:44:46 GMT References: <21936@cup.portal.com> <1082@cernvax.UUCP> <16306@watdragon.waterloo.edu> <RANG.89Sep10184900@derby.cs.wisc.edu> <8399@boring.cwi.nl> <3989@phri.UUCP> <2569@taux01.UUCP> Sender: nobody@orca.WV.TEK.COM Reply-To: andrew@frip.wv.tek.com Organization: Tektronix, Wilsonville, Oregon Lines: 10