Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!ucsdhub!sdcsvax!darrell
From: rrr@leo.UUCP ( Robert R Ramos)
Newsgroups: comp.os.research
Subject: Re: Life with TLB and no PT
Message-ID: <3129@sdcsvax.UCSD.EDU>
Date: Fri, 8-May-87 20:44:43 EDT
Article-I.D.: sdcsvax.3129
Posted: Fri May  8 20:44:43 1987
Date-Received: Sun, 10-May-87 06:06:39 EDT
Sender: darrell@sdcsvax.UCSD.EDU
Organization: CCI CPD (Advanced Development), Irvine CA
Lines: 19
Approved: mod-os@sdcsvax.uucp


In article <3106@sdcsvax.UCSD.EDU>, lamaster@pioneer.arpa (Hugh LaMaster) writes:
> In article <3100@sdcsvax.UCSD.EDU> avie@wb1.cs.cmu.edu (Avadis Tevanian) writes:
> 
> > For example, I just wrote a
> >program that sparsely used 256 megabytes of VM and ran it on my MicroVAX
> >which has only 6 megabytes of physical memory.  [Try *that* on Unix].  The

> mapped sparsely?  Doesn't 4.x BSD allow this?  I confess my ignorance here,
> but MANY virtual memory operating systems allow this...
> 
Of course UNIX can handle large virtual address spaces we regularly run
programs that are over 200MB, doing logical and circuit sinulations.  Only
the default virtrual space in unix systems are small.  In general they are
a configuration parameter, not dynamically allocated.
-- 
"I would rather suffer a cruel and horrible death" Young Sherlock Holmes
	Robert R. Ramos	(rrr)
{allegra!hplabs!felix, ihnp4!trwrb!felix, seismo!rlgvax}!ccicpg!leo!rrr