[net.works.apollo] Virtual Memory Management and Protections

shouhan@sdcsvax.UUCP (Shouhan Wang) (11/06/84)

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