I/O completions port

http://blogs.technet.com/b/winserverperformance/archive/2008/06/26/ Designing-applications-for-high-performance-part-iii.aspx

While in theory the "easy to do", by just calling Kedelayexecutionthread in the "write handler", the system is very likely  To has problems if you do this.  What's the purpose of this delay? Could the data, and hold it while indicating that the data is written, then the a worker thread does the write in Seconds?

You can control the pending of one file, by catching the irp_mj_create you can detect what file it is. You add a context to the file and then in the write calls, you can check for the context and issue the KEDELAYEXECUTIONTHR   ead. There is no samples for something like this, as I said it's a pretty weird requirement, you should being able to use one of The minifilter samples from the WDK as a starting point.

The preoperation callback for the write to the file has identified.

Yes the Mini-filter would see all operations of all processes.  Take the Minispy WDK sample, build and install it. The sample gives you a log of operations.

I/O completions port