Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!att!cbnewsh!dwc
From: dwc@cbnewsh.ATT.COM (Malaclypse the Elder)
Newsgroups: comp.unix.questions
Subject: Re: Virt Mem on V.4
Message-ID: <2059@cbnewsh.ATT.COM>
Date: 10 Jul 89 21:37:05 GMT
References: <1515@ncr-sd.SanDiego.NCR.COM> <1870@auspex.auspex.com> <10499@smoke.BRL.MIL>
Organization: The Legion of Dynamic Discord
Lines: 15

In article <10499@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
> From the AT&T BOF at USENIX recently, I'd say that the region approach
> was totally replaced by VM.  The implication is that SVR4 will be a
> real bitch to port to a system that doesn't have an MMU that conforms
> to the VM model.  E.g. some supercomputers..

from what i have seen of the code, at&t's VM code should not be too
hard to port to non-VM machines.  you just have to make sure that you
will never take a page fault and then the hat routines will mostly be
no-ops.  .  then you just make all the segment drivers no-ops (or
define new segment types).  of course, you'll lose all the nice memory
mapping (e.g. mmap()) system calls.

danny chen
att!hocus!dwc