Hi,
I added a new METHOD_IN_DIRECT ioctl to a kernel mode driver.I changed device object flags to pDeviceObject->Flags| = DO_DIRECT_IO.But when the application send a buffer through this IOCTL call the buffer get as a BUFFERED_IO call. That means pIrp->MdlAddress is NULL and I can see the buffer at pIRP->AsscociatedIrp.SystemBuffer.Am I missing something?Any clue?
Thanks in advance,
Reeja
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
DO_DIRECT_IO has no effect on IOCTLs, only on reads and writes.
Try METHOD_OUT_DIRECT.
Max
----- Original Message -----
From: xxxxx@amd.com
To: NT Developers Interest List
Sent: Wednesday, February 20, 2002 5:08 AM
Subject: [ntdev] DIRECT_IO IOCTL ,driver gets request as a BUFFERED_IO ?
Hi,
I added a new METHOD_IN_DIRECT ioctl to a kernel mode driver.I changed device object flags to pDeviceObject->Flags| = DO_DIRECT_IO.But when the application send a buffer through this IOCTL call the buffer get as a BUFFERED_IO call. That means pIrp->MdlAddress is NULL and I can see the buffer at pIRP->AsscociatedIrp.SystemBuffer.Am I missing something?Any clue?
Thanks in advance,
Reeja
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com