From: "J" <a AT a DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <I%3G5.110185$47 DOT 1397536 AT news DOT bc DOT tac DOT net> <divhusc77sja5ihlmqigi2p47pgdtmc702 AT 4ax DOT com>
Subject: Re: Locking memory
Lines: 27
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Message-ID: <wjdG5.111327$47.1406215@news.bc.tac.net>
Date: Sun, 15 Oct 2000 00:49:41 +0100
NNTP-Posting-Host: 209.53.81.175
X-Complaints-To: news AT bctel DOT net
X-Trace: news.bc.tac.net 971596124 209.53.81.175 (Sun, 15 Oct 2000 00:48:44 PDT)
NNTP-Posting-Date: Sun, 15 Oct 2000 00:48:44 PDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

So basically, I won't need to lock anything unless it's used in an interrupt
handler?

Damian Yerrick wrote in message ...
>On Sat, 14 Oct 2000 14:14:17 +0100, "J" <a AT a DOT com> wrote:
>
>>  I know you are supposed to lock all code and data that is used in
>>a interrupt handler etc.. because of virtual memory swapping data or
>>something along that line. Can somebody clearly explain to me how this
>>all works? Is there any other situation that's non-interrupt releated
>>in which you would want to lock memory also? What I don't understand is
>>why I lock memory in interrupt handlers and not anywhere else. Thanx.
>
>Locking memory makes sure it doesn't get swapped out to disk.  Use it
>to make sure data structures you use often stay in RAM.  Interrupt
>thread code needs data to be locked because a swap operation during
>another DOS call will crash non-reentrant DOS.
>
>--
><O
>( \   GNOME vs. KDE: the game!
> X    http://pineight.8m.com/nes.htm
>
>This is McAfee VirusScan. Add these two lines to your signature to
>prevent the spread of signature viruses.  http://www.mcafee.com/