Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bsu-cs!neubauer
From: neubauer@bsu-cs.bsu.edu (Paul Neubauer)
Newsgroups: comp.arch
Subject: Re: unconventional architectures
Message-ID: <7135@bsu-cs.bsu.edu>
Date: 8 May 89 14:21:35 GMT
References: <112@centaure.UUCP> <422@unicads.UUCP> <11579@cgl.ucsf.EDU> <89May6.165030edt.10782@ephemeral.ai.toronto.edu> <1989May6.234007.23517@utzoo.uucp> <89May7.001514edt.39763@neat.ai.toronto.edu> <40284@think.UUCP>
Reply-To: neubauer@bsu-cs.bsu.edu (Paul Neubauer)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 15

In article <40284@think.UUCP> barmar@kulla.think.com.UUCP (Barry Margolin) writes:
>Multics and Burroughs segments, however, don't get in the way in that
>manner, unless you want to have a single object that doesn't fit in a
>segment (in the case of Multics, the max size is 1MB).  [...]
>
>[...]  In addition, when files are
>mapped into the address space (which is the only way to access files)
>they are assigned unique segments, and applications may allocate

Does this mean that the maximum file size is 1MB?  How difficult does this
make it to deal with, e.g., large databases?

-- 
Paul Neubauer         neubauer@bsu-cs.bsu.edu        neubauer@bsu-cs.UUCP
                      <backbones>!{iuvax,pur-ee}!bsu-cs!neubauer