Xref: news2.mv.net comp.os.msdos.djgpp:5855
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Locking RAM for hardware interrupts
Date: Wed, 10 Jul 1996 08:36:31 CDT
Organization: Rice University, Houston, Texas
Lines: 11
Message-ID: <31e3b1df.sandmann@clio.rice.edu>
References: <836949496 DOT 23711 DOT 0 AT abwillms DOT demon DOT co DOT uk>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> > The routine at a time method is better ...
> Why? Which is 'best'?  Surely locking the image is 'blanket security', 
> without effectively disabling virtual memory?

Certainly locking everything (or just all code) is easier and safer than
doing it a routine at a time.  But this will cause bad paging performance
on systems with insufficient memory (or an outright failure with a 
pagefault if there isn't enough memory to lock).  If you are willing to
put a bigger minimum ram requirement to run your program, that's fine,
but locking only the routines needed would allow the code to potentially
run on a 1Mb box.