Hello Gurus,
The PCI card that I have designed would signal interrupt every 6ms. I
just wonder whether it is possible for my winNT4.0 (on a HPLH3000
Server) to response to the interrupt without skipping over any
interrupt.
In order to shorten the response time, what should I pay attention to
when I am writing the driver?
Thanks in advance.
Best regards,
Jingcao mailto:xxxxx@chinaren.com
Based upon what all developers are supposed to do for ISR routines is for
them to simply acknowledge the interrupt and then queue a Deferred Procedure
Call. Therefore when an Interrupt occurs, your ISR should execute fairly
quickly probably within 10-20 microseconds at the worst. However, you will
need to queue a DPC during your ISR (just like everyone else so that all
Interrupts play fair) and that DPC will do the extended processing of the
interrupt event. That DPC gets placed into a queue and could take several
hundred microseconds to execute while it waits its turn in the Queue. You
should read the DDK and/or some Windows NT driver books about ISR and
DIRQL_LEVEL, DISPATCH_LEVEL and PASSIVE_LEVEL kernel processor levels. Most
Windows NT driver books to a very good job of describing this mechanism.
If you want others to play fair, then you should too!
Dominick
----- Original Message -----
From: “Jingcao Hu”
To: “NT Developers Interest List”
Sent: Thursday, April 20, 2000 5:13 AM
Subject: [ntdev] Questions about interrupt response!
> Hello Gurus,
> The PCI card that I have designed would signal interrupt every 6ms. I
> just wonder whether it is possible for my winNT4.0 (on a HPLH3000
> Server) to response to the interrupt without skipping over any
> interrupt.
> In order to shorten the response time, what should I pay attention to
> when I am writing the driver?
> Thanks in advance.
>
>
>
> Best regards,
> Jingcao mailto:xxxxx@chinaren.com
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@flashcom.net
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>