Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!munnari.oz.au!bruce!trlluna!rhea.trl.oz.au!aduncan
From: aduncan@rhea.trl.oz.au (Allan Duncan)
Newsgroups: comp.sys.amiga
Subject: Re: Memory Protection
Message-ID: <807@trlluna.trl.oz>
Date: 13 Nov 89 02:35:46 GMT
References: <410@mohawk.cs.utexas.edu>
Sender: root@trlluna.trl.oz
Lines: 14

From article <410@mohawk.cs.utexas.edu>, by bryan@cs.utexas.edu (Bryan Bayerdorffer @ Wit's End):

>  And how do you propose to do message 
> passing in the presence of memory protection, hmm?  Either the kernel copies 
> messages between address spaces, or you have to have shared segments that can 
> be read-only for arbitrary groups of processes.  Either way, it's a performance 
> hit.

What is MEMF_PUBLIC for then?

Allan Duncan	ACSnet	aduncan@rhea.trl.oz.au
		ARPA	aduncan%rhea.trl.oz.au@uunet.uu.net
		UUCP	{uunet,hplabs,ukc}!munnari!rhea.trl.oz.au!aduncan
Telecom Research Labs, PO Box 249, Clayton, Victoria, 3168, Australia.