Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!thomas From: thomas@cbmvax.UUCP (Dave Thomas QA) Newsgroups: comp.sys.amiga.tech Subject: Re: MEMF_PHYSICAL? Message-ID: <6914@cbmvax.UUCP> Date: 18 May 89 13:20:53 GMT References: Reply-To: thomas@cbmvax.UUCP (Dave Thomas QA) Organization: Commodore Technology, West Chester, PA Lines: 28 In article deven@rpi.edu (Deven Corzine) writes: > > For those clamoring for a MEMF_PHYSICAL memory requirements flag -- is > this not what MEMF_PUBLIC really is? The RKM isn't so clear, but the > "Amiga Programmer's Handbook" (Sybex) describes the flag as "memory > which can not be swapped out, mapped or otherwise made > nonaddressable." In other words, add to : > > #define MEMF_PHYSICAL MEMF_PUBLIC > > and have a blast... > > If there IS some other distinction, do tell. [perhaps it specifies > physical memory which is publically accessible?] > Deven MEMF_PUBLIC involves memory protection if/when it is ever implemented. Memory which is MEMF_PUBLIC is accessible to multiple tasks. Non MEMF_PUBLIC memory is accessible only to your own task. Of course, currently, MEMF_PUBLIC is not meaningful; all memory is MEMF_PUBLIC. This has nothing to do with virtual memory. MEMF_PHYSICAL would specify memory which must not be swapped out, but this says nothing about accessibility to other tasks. Dave -- Dave Thomas, Commodore Amiga Test Engineering UUCP ...{allegra,rutgers}!cbmvax!thomas