Fw: Re: About time spend when processing Dispatch routine-?

From: “Prekupec Boris” <boris.prekupec>
Sent: Tuesday, May 30, 2000 4:04 PM

> Matt and all others,
> I meant DPC routine(s) first as my driver doesn’t require an interrupt
from
> device to process an I/O operation. It can catch interrupts event but I
> wasn’t able to test that.

I see.

> So I have designed driver to work also through
> IOCTL codes with DeviceIoControl (don’t recall the exact name) function
> call inside win32 application. As I presume that device doesn’t rise
> interrupt I use DPCs as some kind of WatchDog timer.

I’m not quite sure I understand the situation you’re describing but, yes,
direct calls from an application into your driver will occur at
PASSIVE_LEVEL.

> As other routines I also meant I/O routines (StarIo, AdapterControl etc.)
> But I think I have received all answers I needed,
> thanks to you all for your contribution,

Glad to help.

Just be careful in the future how you use the term “dispatch routine”. To
most driver writers, this means an IRP_MJ_* handler which, as I described,
typically has nothing to do with execution at DISPATCH_LEVEL.

- Matt</boris.prekupec>