Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Memory Management
Message-ID: <8711201906.AA25134@cory.Berkeley.EDU>
Date: Fri, 20-Nov-87 14:06:15 EST
Article-I.D.: cory.8711201906.AA25134
Posted: Fri Nov 20 14:06:15 1987
Date-Received: Sun, 22-Nov-87 16:17:34 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 19


    Virtual memory != EachTaskGetsItsOwnAddressSpace

    As far as the Amiga goes, the only compatible solution is a Linear
virtual address space over the entire system.  I.E. addresses are still
unique, tasks are still scatter loaded, and since tasks do NOT have their
own virtual address space, they all start in unique locations and have
the ability to address everything else running in the system.

    Older programs would be upward compatible and actually run with 
full r/w access to the entire system, while newer programs which know 
about the VM will run protected.

    So adding VM/MMU to the Amiga is perfectly O.K.  There is no reason
why we have to conform to the 'standard' way of doing VM.  The idea of
a Linear virtual address space spanning all system objects was brought
to you by.... Zerox Parc of course.

					-Matt