Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Upcoming OSR Seminars:

Writing WDF Drivers I: Core Concepts, Nashua, NH 15-19 May, 2017
Writing WDF Drivers II: Advanced Implementation Tech., Nashua, NH 23-26 May, 2017
Kernel Debugging and Crash Analysis, Dulles, VA 26-30 June, 2017
Windows Internals & Software Driver Development, Nashua, NH 24-28 July, 2017


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 2  
16 Mar 17 12:24
David Chirikutsi
xxxxxx@gmail.com
Join Date: 16 Mar 2017
Posts To This List: 2
Windows filtering platform callout execution time

from this link https://msdn.microsoft.com/en-us/windows/hardware/drivers/network/callout-driver- programming-considerations the classify function should execute as soon as possible. I filtering plackets at layer 2 but I want to wait for the user app to reply with allow or block action and in my classify function I will only wait for 5 seconds and if the user app delays then it continues by the block action but I want to know if 5 seconds is too much for the classify function running at dispatch_level to wait or I should just proceed
  Message 2 of 2  
16 Mar 17 12:57
Peter Scott
xxxxxx@kerneldrivers.com
Join Date: 17 Feb 2012
Posts To This List: 48
Windows filtering platform callout execution time

You won't be able to block directly within your classify function at=20 dispatch level, at least not waiting for a user mode response. You'll=20 need to queue these requests up to a worker and then process them=20 asynchronously, similar to how the stream edit (stmedit) sample in the=20 DDK functions. Pete -- Kernel Drivers Windows File System and Device Driver Consulting www.KernelDrivers.com 866.263.9295 ------ Original Message ------ From: xxxxx@gmail.com To: "Windows System Software Devs Interest List" <xxxxx@lists.osr.com> Sent: 3/16/2017 10:25:22 AM Subject: [ntdev] Windows filtering platform callout execution time >from this link=20 >https://msdn.microsoft.com/en-us/windows/hardware/drivers/network/callout-= driver-programming-considerations >the classify function should execute as soon as possible. I filtering=20 >plackets at layer 2 but I want to wait for the user app to reply with=20 >allow or block action and in my classify function I will only wait for=20 >5 seconds and if the user app delays then it continues by the block=20 >action but I want to know if 5 seconds is too much for the classify=20 >function running at dispatch_level to wait or I should just proceed > >--- >NTDEV is sponsored by OSR > <...excess quoted lines suppressed...>
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 09:57.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license