Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!ji.Berkeley.EDU!shs
From: shs@ji.Berkeley.EDU (Steve Schoettler)
Newsgroups: comp.sys.amiga
Subject: Re: Real-time vs. Virtual Memory
Message-ID: <21809@ucbvax.BERKELEY.EDU>
Date: Mon, 16-Nov-87 19:12:03 EST
Article-I.D.: ucbvax.21809
Posted: Mon Nov 16 19:12:03 1987
Date-Received: Thu, 19-Nov-87 00:07:38 EST
References: <74@mithras> <1053@sugar.UUCP> <113@citcom.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: shs@ji.Berkeley.EDU.UUCP (Steve Schoettler)
Organization: University of California, Berkeley
Lines: 15
Keywords: paging virtual memory real time
Summary: not a problem

In article <113@citcom.UUCP> jack@citcom.UUCP (Jack Waugh) writes:
>> Virtual memory and real-time don't get along.
>
>Why not side-by-side?  Keep your real-time system, and
>allocate some memory to a virtual memory system that
>would run at lower priority.

Yeeeech!

VM and real time work together just fine.  If you're waiting for an important
event, simply tell the system not to page you out.

How do you think the operating system keeps from paging out the paging code? :-)

Steve