Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mailrus!iuvax!rutgers!cbmvax!valentin From: valentin@cbmvax.commodore.com (Valentin Pepelea) Newsgroups: comp.sys.amiga.tech Subject: Re: Memory Protection! Message-ID: <13756@cbmvax.commodore.com> Date: 10 Aug 90 19:56:24 GMT References: <1145.26bd4989@waikato.ac.nz> <13693@cbmvax.commodore.com> Reply-To: valentin@cbmvax (Valentin Pepelea) Organization: Commodore, West Chester, PA Lines: 31 In article hclausen@adspdk.CBMNET (Henrik Clausen) writes: > > Now, if a few hooks where in there to allow applications to explicitly ask >for protected,virtual and non-shareable memory, (AllocVMem() ?) they could >benefit on the larger machines, while still running on non-MMU machines. > ... > They would still use AllocMem() for message ports and whatever else is >going to be shared with other tasks. > ... > For non-MMU machines, these calls would behave just like AllocMem(), >apart from the resource tracking. > ... > Would this break anyone? Valentin? Providing new functions with added functionality cannot break any existing programs. But embarking on such a venture requires energy, intitiative and presence of clear mind which not everybody has. Another problem is that even if you provide the possiblity for new applications to run protected within the environment, the fact that older programs cann still jog around the address space and wreak havoc, defeats the initial purpose. Either you provide memory protection to everybody simultaneoulsy, or you don't at all. Valentin -- The Goddess of democracy? "The tyrants Name: Valentin Pepelea may distroy a statue, but they cannot Phone: (215) 431-9327 kill a god." UseNet: cbmvax!valentin@uunet.uu.net - Ancient Chinese Proverb Claimer: I not Commodore spokesman be