Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!mips!bridge2!jarthur!nntp-server.caltech.edu!tybalt.caltech.edu!toddpw
From: toddpw@tybalt.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.sys.apple2
Subject: Re: ViM
Keywords: Virtual Memory, GS, memory.
Message-ID: <1990Oct2.105027.9723@nntp-server.caltech.edu>
Date: 2 Oct 90 10:50:27 GMT
References: <9009291730.aa10320@generic.UUCP> <1990Oct1.200647.18425@uokmax.ecn.uoknor.edu>
Sender: news@nntp-server.caltech.edu
Organization: California Institute of Technology, Pasadena
Lines: 12
Nntp-Posting-Host: tybalt.caltech.edu


Mail me a rough description of your swapping algorithm. I need to know what
gets swapped out and when. Virtual memory in software is a royal pain in the
rear unless your programs are written to expect it and you could fact some
serious compatability problems.

Most applications that I have seen are either totally memory resident or they
use segments, a semi-voluntary form of virtual memory that is required for
large programs...

Todd Whitesel
toddpw @ tybalt.caltech.edu