Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.arch
Subject: Re: Multics & Memory mapped files
Message-ID: <4810@scolex.sco.COM>
Date: 12 Feb 90 21:00:04 GMT
References: <8859@portia.Stanford.EDU> <20571@watdragon.waterloo.edu> <49956@sgi.sgi.com> <4791@helios.ee.lbl.gov> <2093@crdos1.crd.ge.COM> <1990Feb7.221800.804@utzoo.uucp> <2106@crdos1.crd.ge.COM> <5180@crdgw1.crd.ge.com> <2115@crdos1.crd.ge.COM>
Reply-To: seanf@sco.COM (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 16

In article <2115@crdos1.crd.ge.COM> davidsen@crdos1.crd.ge.com (bill davidsen) writes:
>  You're right, but in general it doesn't matter. I looked over files on
>about 200 Suns for large files, and the largest single file was under
>100MB. Therefore for most applications there isn't a problem.

Except, of course, that Sun's MMUs don't work with very large virtual
memories, either.  I think the Sun-2 had a limit of 16Mb, of course (68010),
and the early Sun-3's, at least, had a limit of 64 or 128Mb per process.

I could be wrong, of course, but I don't believe they supported all 32
virtual address bits.

-- 
Sean Eric Fagan  | "Time has little to do with infinity and jelly donuts."
seanf@sco.COM    |    -- Thomas Magnum (Tom Selleck), _Magnum, P.I._
(408) 458-1422   | Any opinions expressed are my own, not my employers'.