Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!grebyn!ckp
From: ckp@grebyn.com (Checkpoint Technologies)
Newsgroups: comp.sys.amiga.tech
Subject: Re: DMA in VM
Message-ID: <14065@grebyn.com>
Date: 1 Dec 89 16:38:42 GMT
References: <14059@grebyn.com> <2054@atanasoff.cs.iastate.edu> <14060@grebyn.com> <VINSCI.89Dec1030202@ra.abo.fi>
Reply-To: ckp@grebyn.UUCP (Checkpoint Technologies)
Organization: Grebyn Timesharing, Vienna, VA, USA
Lines: 12

In article <VINSCI.89Dec1030202@ra.abo.fi> vinsci@ra.abo.fi (Leonard Norrgard) writes:
>>Laugh if you like. In VAX/VMS, every part of a process is virtual
>>memory, including any IO buffering. The IO system takes care of ensuring
>>that such pages are resident and locked for the duration of a DMA IO
>>transfer.
>
>  Not necessarily. But unless you have done systems programming under
>VAX/VMS, it is unlikely that you ever have seen anything else than
>virtual memory.

	Well, as it happens, I have written a VMS DMA device driver... I
think that qualifies as 'systems programming'...