🚀 go-pugleaf

Path: steinmetz!jesup
From: jesup@steinmetz.steinmetz.UUCP (Randell Jesup)
Newsgroups: mod.computers.68k
Subject: Re: Submission for mod-computers-68k
Message-ID: <1262@steinmetz.steinmetz.UUCP>
Date: 4 Mar 87 22:13:00 GMT
References: <8702262018.AA16981@watcgl.uucp>
Reply-To: jesup@kbsvax.steinmetz.UUCP (Randell Jesup)
Distribution: world
Organization: General Electric CRD, Schenectady, NY
Lines: 20

In article <8702262018.AA16981@watcgl.uucp> drforsey@watcgl.waterloo.edu (Dave Forsey) writes:
>There is perhaps a deeper reason for the amiga not using a MMU. The operating
>system is based on message passing, those messages are passed by reference
>rather than copying. It assumes and is dependent on an single address space.
>Unless the OS changes in a major way you'll not get VM on an Amiga.
>
>Dave Forsey

	There is SOME support for seperate address spaces for different
processes.  When you allocate memory, the type you can get are FAST, CHIP,
and PUBLIC.  CHIP is accessable by the custom chips, FAST isn't, and PUBLIC
is guarenteed to be accessable by other processes.  Of course, there probably
are a lot of programs that just take any memory at all when allocating
messages, etc, but the basic support is there.

	Randell Jesup
	jesup@steinmetz.uucp
	jesup@ge-crd.arpa