morrison@cs.ubc.ca (Rick Morrison) (12/18/89)
I have been pouring over the Mach documentation provided with the
NeXT. It is vaguely suggested (Ch 16 of the NeXT Ref Man) that an
alternate pager object may be associated with a task. Further reading
tends to falsify this suggestion, and there doesn't appear to be any
evidence (e.g. in proc.h) that this is supported in the version of Mach
running on the NeXT.
Do other implementations of Mach allow alternate
pagers or have I just encountered forward references to features
not yet supported?
---------------
Rick Morrison | {alberta,uw-beaver,uunet}!ubc-cs!morrison
Dept. of Computer Science| morrison@cs.ubc.ca
Univ. of British Columbia| morrison%ubc.csnet@csnet-relay.arpa
Vancouver, B.C. V6T 1W5 | morrison@ubc.csnet (ubc-csgrads=128.189.97.20)
(604) 228-4327Richard.Draves@CS.CMU.EDU (12/20/89)
Excerpts from netnews.comp.os.mach: 17-Dec-89 Pager Objects Rick Morrison@cs.ubc.ca (772) > I have been pouring over the Mach documentation provided with the > NeXT. It is vaguely suggested (Ch 16 of the NeXT Ref Man) that an > alternate pager object may be associated with a task. Further reading > tends to falsify this suggestion, and there doesn't appear to be any > evidence (e.g. in proc.h) that this is supported in the version of Mach > running on the NeXT. > Do other implementations of Mach allow alternate > pagers or have I just encountered forward references to features > not yet supported? The NeXT 1.0 VM system is based on the Mach 2.0 release from CMU. It doesn't support external memory managers (pagers). (This support was still experimental in Mach 2.0.) The external memory management interface is standard in Mach 2.5. This interface allows user tasks to act as servers for memory objects, and allows other user tasks to map these memory objects into their address spaces. I don't know when NeXT plans to release a kernel that supports external memory management. Rich