Date: Thu, 8 Jun 2000 00:02:51 +0530 (IST) Message-Id: <200006071832.AAA16516@bgl2.vsnl.net.in> From: Prashant TR To: ryan4600 AT my-deja DOT com CC: djgpp AT delorie DOT com In-reply-to: <8hjj65$flt$1@nnrp1.deja.com> (ryan4600@my-deja.com) Subject: Re: Keyboard Handler problem References: <8hiia1$lvs$1 AT nnrp1 DOT deja DOT com> <200006061335 DOT TAA29025 AT bgl2 DOT vsnl DOT net DOT in> <8hjj65$flt$1 AT nnrp1 DOT deja DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > IMO, it is best to just make a note of what key was pressed (store > > that in a queue, probably). Later, the program would make checks for > > necessary keys. Bloating the interrupt handler code can cause strange > > problems (especially for timer interrupts). > > > > Also, lock any data that you may be using for obvious reasons. > > > I am thinking about disabling all virtual memory for now. I now this > might make things slower in the real world, but is safer for learning > purposes.. How can this be? Locked data/code should run faster since they always lie in the physical memory. So by disabling VM (using _CTR0_FLAG_LOCKALL) you are actually making things faster. And to me it looks like a good idea since most systems today generally have at least 32/64M or RAM which is far too much for most applications.