Memory Allocation/Virtual Memory

Article View: comp.sys.amiga.tech

Article #9677

Back to comp.sys.amiga.tech Previous Next

#9677

From: Tomas G. Rokicki
Date: Fri, 02 Sep 1988 17:44

12 lines
857 bytes

Worried about programs breaking because they didn't MEMF_PUBLIC?
Fine.  We need to add a MEMF_DMA flag anyway (the 2090 can't
touch at least the Hurricane '020 memory; the software works,
though, just fine, in copying the data, so don't think it breaks)
so why not add a MEMF_PRIVATE flag, where the default is MEMF_PUBLIC?
All current programs would be loaded completely shared, as they
are now, and could stomp on each other.  New versions, though,
could MEMF_PRIVATE to get safe areas . . .

It's just a thought.

-tom

Technical Details

Message-ID: <3813@polya.Stanford.EDU>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att!ucbvax!decwrl!labrea!polya!rokicki

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att!ucbvax!decwrl!labrea!polya!rokicki
From: rokicki@polya.Stanford.EDU (Tomas G. Rokicki)
Newsgroups: comp.sys.amiga.tech
Subject: Memory Allocation/Virtual Memory
Message-ID: <3813@polya.Stanford.EDU>
Date: 2 Sep 88 17:44:42 GMT
Organization: Stanford University
Lines: 12