Article View: comp.sys.amiga.tech
Article #12742Re: MEMF_PHYSICAL?
From: Dave Thomas QA
Date: Thu, 18 May 1989 13:20
Date: Thu, 18 May 1989 13:20
28 lines
1612 bytes
1612 bytes
In article <DEVEN.89May18024329@daniel.rpi.edu> 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 <exec/memory.h>:
>
> #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
Technical Details
Message-ID:
<6914@cbmvax.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!thomasReferences:
<DEVEN.89May18024329@daniel.rpi.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!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: <DEVEN.89May18024329@daniel.rpi.edu> Reply-To: thomas@cbmvax.UUCP (Dave Thomas QA) Organization: Commodore Technology, West Chester, PA Lines: 28