Sounds good to me. But the Fat sources have code to post a Create, and the
dispatch routine for the worker thread has a case for IRP_MJ_CREATE. It’s
quite possible, now that I think of it, that this code is never exercised,
but …
Thanks,
Curt
-----Original Message-----
From: Jamey Kirby [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, August 23, 2000 2:06 PM
To: File Systems Developers
Subject: [ntfsd] RE: What’s the value of non-read/write async handling ?
Create calls are sync. So, why post to a thread? Isn’t this extra work?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@omnishift.com
Sent: Wednesday, August 23, 2000 2:07 PM
To: File Systems Developers
Subject: [ntfsd] RE: What’s the value of non-read/write async handling ?
Hi Daniel:
Okay, I understand wrt the create (supersede/overwrite) that you want to
defer to; thanks.
In general, though, why post when the resource can’t be acquired exclusively
right now? A Create request, for example: why not just call
ExAcquireResourceExclusive() with Wait == TRUE; what purpose is there for
calling it without blocking, then posting it for a system thread to acquire
it with blocking?