IOCP and the there thread pool is a model that allows you to scale up your UM process by breaking up your synchronous functions that use blocking IO into distinct units of work and reducing context switches - the same threads keep running, even though they process data from different requests
None of this affects the KM design as all of your IOCTLs that cannot complete immediately must by async anyways (STATUS_PENDING)
Sent from Surface Pro
From: PScott
Sent: Friday, July 31, 2015 10:59 AM
To: Windows File Systems Devs Interest List
If you want to play around with an alternative model then implement an
inverted-call design using IOCtls. Keep completion ports out of it for
the first phase until you get the basic design in place.
Pete
–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com http:</http:>
866.263.9295
------ Original Message ------
From: xxxxx@gmail.com
To: “Windows File Systems Devs Interest List”
Sent: 7/31/2015 7:01:11 AM
Subject: RE:[ntfsd] Alternative FltSendMessage
>Thank you Alexandru!
>In sample (scanner from DDK) FilterGetMessage using with
>CompletionPort(), what’s the point of this? And how I can use
>CompletionPort() with DeviceIoControl( inverted-call model)?
>
>
>—
>NTFSD is sponsored by OSR
>
>OSR is hiring!! Info at http://www.osr.com/careers
>
>For our schedule of debugging and file system seminars visit:
>http://www.osr.com/seminars
>
>To unsubscribe, visit the List Server section of OSR Online at
>http://www.osronline.com/page.cfm?name=ListServer
—
NTFSD is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
For our schedule of debugging and file system seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer