Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!UOTTAWA.BITNET!451061 From: 451061@UOTTAWA.BITNET (Valentin Pepelea) Newsgroups: comp.sys.amiga.tech Subject: Re: MEMF_PHYSICAL? Message-ID: <8906160430.AA09545@jade.berkeley.edu> Date: 16 Jun 89 03:23:13 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 29 Kristoffer Eriksson writes in message <1251@pkmab.se> > > How can the OS and MMU provide any protection, if they don't care what > program is using what memory? Imagine the Unix OS where each program has its own addressing space. Every program then has its virtual pages mapped either onto disk, or onto some scattered chunks of physical memory. Each program therefore has its own translation table which maps a virtual addressing range starting at 0. On a single addressing space OS, you have the exact same thing, except that rather than having the virtual addresses start at 0, they start at arbitrary and exclusive locations. This is not the ideal implementation, but it is the best one the 68851 can offer. If I were allowed to design my own MMU, I would use a single translation table, where each page descriptor entry would also contain an "owner" field. This owner field would then be compared to the current task ID, and thus the access priviledge would be determined. Easy thing to design, but since the 68030 & 68040 have 68851-like MMUs already built in, this would be a waisted effort. Valentin _________________________________________________________________________ "An operating system without Name: Valentin Pepelea virtual memory is an operating Phonet: (613) 231-7476 (New!) system without virtue." Bitnet: 451061@Uottawa.bitnet Usenet: Use cunyvm.cuny.edu gate - Ancient Inca Proverb Planet: 451061@acadvm1.UOttawa.CA