Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!quintus!ok
From: ok@quintus.UUCP (Richard A. O'Keefe)
Newsgroups: comp.arch
Subject: Re: VM needed for rapid startup
Keywords: paging virtual-memory speed
Message-ID: <1016@cresswell.quintus.UUCP>
Date: 25 May 88 05:34:02 GMT
References: <463@cvaxa.sussex.ac.uk>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 11

In article <463@cvaxa.sussex.ac.uk>, aarons@cvaxa.sussex.ac.uk (Aaron Sloman) writes:
> Perhaps there are memory management techniques I am unaware of that
> make it easy for portions of a large program to be read in as required,
> without the cost of full virtual memory.

It depends on whether you identify "virtual memory" with paging:
in a (genuine, not INTEL) segmented sytem (think of the OOZE system)
you can bring into physical memory just the objects you currently need.
The B6700 could and did page large data arrays, but it couldn't page
code.  Since each procedure was a separately swappable segment, that
didn't matter much.  No page tables, but easy partial loading.