From:	Damian Yerrick <Bullcr_pd_yerrick AT hotmail DOT comRemoveBullcr_p>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Locking memory
Organization:	Pin Eight Software http://pineight.8m.com/
Message-ID:	<divhusc77sja5ihlmqigi2p47pgdtmc702@4ax.com>
References:	<I%3G5.110185$47 DOT 1397536 AT news DOT bc DOT tac DOT net>
X-Newsreader:	Forte Agent 1.7/32.534
MIME-Version:	1.0
Lines:	21
X-Trace:	/KiKeWee8jE/d1sKhEkTrRBTSY7Xj0o6RbInbXDe0Ep26J/LZJs5OsAcuxkDostw9YLxPPxoJTIa!55CKyV8n313USJMDH31s2yEQhefPFyaiRYcwEtNpKzoekW6pxgh/Yagh0SKCDw1/cdD1L/mkHQFs!lu2T
X-Complaints-To:	abuse AT gte DOT net
X-Abuse-Info:	Please be sure to forward a copy of ALL headers
X-Abuse-Info:	Otherwise we will be unable to process your complaint properly
NNTP-Posting-Date:	Sun, 15 Oct 2000 00:50:19 GMT
Distribution:	world
Date:	Sun, 15 Oct 2000 00:50:19 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

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/

- Raw text -