Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!purdue!tut.cis.ohio-state.edu!ucbvax!EE.ECN.PURDUE.EDU!bevis
From: bevis@EE.ECN.PURDUE.EDU (Jeff Bevis)
Newsgroups: comp.sys.amiga
Subject: Re: Memory Protection
Message-ID: <8911180206.AA22553@en.ecn.purdue.edu>
Date: 18 Nov 89 02:06:33 GMT
Article-I.D.: en.8911180206.AA22553
References: <807@trlluna.trl.oz>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Purdue University Engineering Computer Network
Lines: 17

In article <807@trlluna.trl.oz>, aduncan@rhea.trl.oz.au (Allan Duncan) writes:
>From article <410@mohawk.cs.utexas.edu>, by bryan@cs.utexas.edu (Bryan Bayerdorffer @ Wit's End):
>
>What is MEMF_PUBLIC for then?
>
This flag specifies that you want memory (chip or fast) which is 
guaranteed not to be swapped out or become unavailable to all processes all
the time.  You will want this type of memory for I/O operations (buffers,
things the OS will look at).  It's not of any consequence to ignore this
flag NOW.  But when Amiga/VM arrives -- oh, the software that will break!
So be sure to use it when appropriate.


+--------------------------------+--------------------------------------------+
| Jeff Bevis 		         | "But I don't like spam!"		      |
| bevis@en.ecn.purdue.edu	 | 	     Give me Amiga or nothing at all. |
+--------------------------------+--------------------------------------------+