home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!olivea!spool.mu.edu!agate!stanford.edu!kronos.arc.nasa.gov!iscnvx!netcomsv!terapin!paulk
- From: paulk@terapin.com (Paul Kienitz)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: physical memory protection with MMU
- Message-ID: <paulk.28d4@terapin.com>
- Date: 17 Nov 92 02:44:18 GMT
- References: <1e752hINNk3h@darkstar.UCSC.EDU>
- Organization: BBS
- Lines: 12
-
- > The real problem stems for two (or more) tasks that pass their own
- > privately defined structures around.
-
- I must disagree. Since so many programs pass so much memory between
- tasks both in system defined ways and in private ways, the odds are
- that you'll end up with memory protection that leaves unprotected a
- significant fraction of all memory in use. Another concern is
- performance ... one MUST retain the ability to pass Exec messages in
- near zero time, for currenps to work well. My MIDI sequencer,
- for instance, can easily pass a single message through a dozen
- different tasks between the press of a key and the sounding of the
- resulting note. That has to be done QUICKLY.
-