Newsgroups:	comp.os.msdos.djgpp
From:	Peter Berdeklis <peter AT atmosp DOT physics DOT utoronto DOT ca>
Subject:	Re: Interrupts Maximum Rate
Message-ID:	<Pine.SGI.3.91.970410183107.1012A-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
Organization:	University of Toronto - Dept. of Physics
In-Reply-To:	<334D0181.3D05@eev.e-technik.uni-erlangen.de>
Date:	Thu, 10 Apr 1997 22:36:29 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> <Pine DOT SGI DOT 3 DOT 91 DOT 970409112749 DOT 17572A-100000 AT atmosp DOT physics DOT utoronto DOT ca> <334D0181 DOT 3D05 AT eev DOT e-technik DOT uni-erlangen DOT de>
Lines:	30
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Thu, 10 Apr 1997, Schuster wrote:
> Here the results:
> 
> P120 - Triton I chipset (Intel): 58 kHz
> 486 DX50 (AMD): 35 kHZ
> 
> Additional, if I do 12 imports (0 WS) in the Handler, the result is:
> 
> P120 - Triton I chipset (Intel): 40 kHz
> 486 DX50 (AMD): 22 kHZ
> 
> ... Just in case, somebody wants to know.
> (Perhaps an update in the FAQ, Eli?)

Neat.

However, I think the problem addressed by the FAQ is not so much the 
maximum interrupt freq, but how high a freq before you notice a 
significant lag in your (non-trivial) program running in the foreground.  
This is not the case in your experiment I think, or am I wrong?

Of course the rule of thumb offered by the FAQ may vary with program 
type.  A program that does a lot of waiting for user input could probably 
use your timings, but a CPU intensive prog might have noticable lag even 
below 10 kHz.

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

- Raw text -