delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/10/14/17:15:12

From: "J" <a AT a DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Locking memory
Lines: 9
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Message-ID: <I%3G5.110185$47.1397536@news.bc.tac.net>
Date: Sat, 14 Oct 2000 14:14:17 +0100
NNTP-Posting-Host: 207.194.23.183
X-Complaints-To: news AT bctel DOT net
X-Trace: news.bc.tac.net 971557992 207.194.23.183 (Sat, 14 Oct 2000 14:13:12 PDT)
NNTP-Posting-Date: Sat, 14 Oct 2000 14:13:12 PDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello,
  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.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019