Re: IWDFIoRequest::ForwardToIoQueue does not return immediately
- From: "Doron Holan [MSFT]" <doronh@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Dec 2007 16:57:20 -0800
do not block in the queue you are forwarding to. in the final fwd'ed queue, return and complete the reques later when conditions are correct to complete it
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.
"Andre" <Andre@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3C7DD180-CA4A-4FE2-8834-6CACF16B03F5@xxxxxxxxxxxxxxxx
Hello,
I am using different IoQueues for read, write, and IoControl requests in an
UMDF driver. A request is first handled by an DefaultIoHandler and then
forwarded to its respective queue using the method
IWDFIoRequest::ForwardToIoQueue. I would expect, that this method returns
immediately after it requeued the request, but instead the request is handled
in the context of ForwardToIoQueue. Therefore, the call blocks until the
request has been completed. This happens even when forwarding over multiple
queues. Note, that these queues are configure with
WdfIoQueueDispatchParallel or WdfIoQueueDispatchSequential.
I suppose I could use manual queues from which I can retrieve requests in a
thread separately created by my driver, to decouple the actual processing
from the request. Is this the recommended way?
What is the point of forwarding, if it does not return immediately?
Thanks in advance for any comments or sugestions!
Regards,
Andre
.
- Follow-Ups:
- Prev by Date: Re: Device Path Exerciser thread doesn't stopped
- Next by Date: Re: Application sample for UVC extension units
- Previous by thread: Re: Device Path Exerciser thread doesn't stopped
- Next by thread: Re: IWDFIoRequest::ForwardToIoQueue does not return immediately
- Index(es):
Relevant Pages
|
Loading