home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ornl!rsg1.er.usgs.gov!darwin.sura.net!spool.mu.edu!umn.edu!csus.edu!netcom.com!netcomsv!terapin!paulk
- From: paulk@terapin.com (Paul Kienitz)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: physical memory protection with MMU
- References: <1duvk4INN65q@darkstar.UCSC.EDU>
- Message-ID: <paulk.27ok@terapin.com>
- Date: 15 Nov 92 11:37:03 PST
- Organization: BBS
- Lines: 12
-
- > The real problem with memory protection on the Amiga is that it is
- > possible for one task to share its memory with another without
- > explicitly telling the OS that the shared memory is in fact shared.
- > This is a big nono under a protected OS. However, it is an
- > exaggeration to say that 99.9% of Amiga programs do this.
-
- Almost every program shares memory -- any time you do IO at either
- the dos or exec level, any time you listen to IDCMP events, or look
- at any system list, you're sharing memory between tasks.
-
- But of course, we ALWAYS remember to use MEMF_PUBLIC in those cases,
- right?
-