Article View: net.works.apollo
Article #12Virtual Memory Management and Protections
From: Shouhan Wang
Date: Tue, 06 Nov 1984 02:39
Date: Tue, 06 Nov 1984 02:39
23 lines
1428 bytes
1428 bytes
I am working on my term paper in which I need to know some
internal informaton about Apollo's Aegis.
The followings are what I am interested, if any body may
supply these information, I will appreciate very much.
(1) How many bits are used in the virtual memory addressing,
(2) Does the Virtual Memory pages processes's page table?
(3) Whether system pages are sharable, i.e. as VMS?
(4) What replacement policy is used, i.e. LRU, WS, etc.?
(5) Are cluster of pages fetched when a page fault occures?
(6) Is any descriptor scheme used and how does it work?
(7) How the subsystem data files are protected?
(8) Are the user library files binded at the last moment?
i.e. at load time?
From the sau1/aegis.map I assume that Aegis uses COLD
START to swap in a new process, is this true?
My mailing address is: ucbvax!sdcsvax!shouhan
ShouHan Wang
Technical Details
Message-ID:
<449@sdcsvax.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!watmath!clyde!bonnie!akgua!sdcsvax!shouhanShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site sdcsvax.UUCP Path: arc1-ca.pugleaf.net!utzoo!watmath!clyde!bonnie!akgua!sdcsvax!shouhan From: shouhan@sdcsvax.UUCP (Shouhan Wang) Newsgroups: net.works.apollo Subject: Virtual Memory Management and Protections Message-ID: <449@sdcsvax.UUCP> Date: Mon, 5-Nov-84 21:39:25 EST Article-I.D.: sdcsvax.449 Posted: Mon Nov 5 21:39:25 1984 Date-Received: Thu, 8-Nov-84 00:46:21 EST Distribution: net Organization: EECS Dept. U.C. San Diego Lines: 24