Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!teknowledge-vaxc!sri-unix!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: <1023@cresswell.quintus.UUCP>
Date: 26 May 88 07:37:10 GMT
References: <463@cvaxa.sussex.ac.uk> <1016@cresswell.quintus.UUCP> <508@cmx.npac.syr.edu>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 13
Posted: Thu May 26 00:37:10 1988

In article <1016@cresswell.quintus.UUCP> I wrote
> 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.
> 
In article <508@cmx.npac.syr.edu>, billo@cmx.npac.syr.edu (Bill O) writes:
> The B6700, at least the one that I knew and loved :-), did not do
> "paging" of either data or code.
Yes, it did page sufficiently large arrays.  Look in the index under
"segmented arrays".  I think the page size was 256 48-bit words.  (It
was never quite clear from the manuals which things were written to disc
with tag bits and which things were written without.  Fortunately users
never needed to know.)  "DIRECT" and "VALUE" arrays were not paged.