Re: Passive in arbitrary context?
- From: "Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Jul 2006 20:14:17 -0700
and typically you don't sleep in the context, you pend the irp and do the
work later.
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx> wrote in message
news:%23tAaPe0rGHA.4296@xxxxxxxxxxxxxxxxxxxxxxx
Dispatch routines of the topmost driver are running in the app's
thread,
the thread which called Read/WriteFile or DeviceIoControl.
PnP and Power dispatch routines are running in system thread context,
so
are any work items queued by ExQueueWorkItem.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com
<BubbaGump> wrote in message
news:e7v9c2t2q7j98s41eu784bki1juv4qgq7r@xxxxxxxxxx
Do some driver routines run in an arbitrary thread context even though
they're called at passive level? (as opposed to the context of the
user thread that requested them or some system thread) Does that mean
that whenever such a routine sleeps, it steals part of the quantum of
a thread that really doesn't care anything about it?
.
- Follow-Ups:
- Re: Passive in arbitrary context?
- From: Maxim S. Shatskih
- Re: Passive in arbitrary context?
- References:
- Passive in arbitrary context?
- From: BubbaGump
- Re: Passive in arbitrary context?
- From: Maxim S. Shatskih
- Passive in arbitrary context?
- Prev by Date: Re: Enumerating CFI capable devices
- Next by Date: Re: Question about SetupDiGetClassDevs and SetupDiEnumDeviceInterfaces
- Previous by thread: Re: Passive in arbitrary context?
- Next by thread: Re: Passive in arbitrary context?
- Index(es):
Relevant Pages
|