From: ····@su-russell.UUCP
Subject: Re: autoload (was: Re: Against the Tide of Common LISP)
Date: 
Message-ID: <257@su-russell.ARPA>
When I said that Unix didn't handle VM well, I was refering to SUN
Unix. I wasn't complaining about locality problems - any virtual
memory system has a problem with scattered references.

I was complaining about the need to have the maximum amount of
swapping space (I tend to call it paging space) needed by a process
available at image startup. I've frequently been unable to run a Lisp
on the SUN because Unix doesn't think it has enough swapping space.

I also wish that Unix had features like copy-on-write and demand-zero
pages.
From: Bruce Robertson
Subject: Re: autoload (was: Re: Against the Tide of Common LISP)
Date: 
Message-ID: <652@stride.Stride.COM>
In article <···@su-russell.ARPA> ····@su-russell.ARPA (Wade Hennessey) writes:
>I also wish that Unix had features like copy-on-write and demand-zero
>pages.

Much as I dislike System V, the virtual memory system provided by AT&T
does not require you to have enough swap space to contain the process
no matter how big it might get, and it does have copy-on-write and
demand-zero pages.  Because of copy-on-write, data pages are stored in
the page cache as well as text pages, resulting in commonly used
programs starting up much more quickly.

In fact, we are using the System V virtual memory implementation in
the 4.3bsd port that we are working on, rather than Berkeley's
implementation.
-- 

	Bruce Robertson
	·····@stride.Stride.COM
	cbosgd!utah-cs!utah-gr!stride!brucad