Newsgroups: comp.os.msdos.djgpp
From: Peter Berdeklis <peter AT atmosp DOT physics DOT utoronto DOT ca>
Subject: Re: Interrupts (Hardware) 
Message-ID: <Pine.SGI.3.91.970409112749.17572A-100000@atmosp.physics.utoronto.ca>
Nntp-Posting-Host: chinook.physics.utoronto.ca
Sender: news AT info DOT physics DOT utoronto DOT ca (System Administrator)
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Organization: University of Toronto - Dept. of Physics
In-Reply-To: <334A5E67.2E34@eev.e-technik.uni-erlangen.de> 
Date: Wed, 9 Apr 1997 15:32:35 GMT
References: <Pine DOT SUN DOT 3 DOT 95 DOT 970406144445 DOT 11066A-100000 AT rainbow> <Pine DOT SGI DOT 3 DOT 91 DOT 970407142951 DOT 17332A-100000 AT atmosp DOT physics DOT utoronto DOT ca> <334A5E67 DOT 2E34 AT eev DOT e-technik DOT uni-erlangen DOT de> 
Lines: 20
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Tue, 8 Apr 1997, Schuster wrote:
> I'm reading 12 input-values with the ISA Bus via Hadware interrupts at a
> frequency 
> of ~12khz and a simple PM Handler, also I do some graphics (with
> Allegro) on 
> the screen- works fine with a P90...

The FAQ suggests that anything more than 10Khz might need a RM handler as 
well.  However, if you've got a P90 then the extra clock cycles probably 
aren't a big deal.

The graphics won't affect interrupt latency at all.  The graphics code is 
just interrupted.  In fact, most graphics code is slow not because of the 
CPU time it uses but because the bus is slow (ray tracing is an obvious 
exception).

---------------
Peter Berdeklis
Dept. of Physics, Univ. of Toronto