Dokan IO Event. More...
#include <dokani.h>
Data Fields | |
| PDOKAN_INSTANCE | DokanInstance |
| PDOKAN_OPEN_INFO | DokanOpenInfo |
| PEVENT_INFORMATION | EventResult |
| ULONG | EventResultSize |
| BOOL | PoolAllocated |
| DOKAN_FILE_INFO | DokanFileInfo |
| PEVENT_CONTEXT | EventContext |
| PDOKAN_IO_BATCH | IoBatch |
Detailed Description
Dokan IO Event.
Use to track one of the even pulled by DOKAN_IO_BATCH while it is being processed by the FileSystem. The EventContext is owned by the DOKAN_IO_BATCH and not this instance.
Field Documentation
| DOKAN_FILE_INFO PDOKAN_IO_EVENT::DokanFileInfo |
File information for the event context
| PDOKAN_INSTANCE PDOKAN_IO_EVENT::DokanInstance |
Dokan instance linked to the event
| PDOKAN_OPEN_INFO PDOKAN_IO_EVENT::DokanOpenInfo |
Optional open information for the event context
| PEVENT_CONTEXT PDOKAN_IO_EVENT::EventContext |
The actual event pulled from the kernel. This buffer is not owned by the IoEvent.
| PEVENT_INFORMATION PDOKAN_IO_EVENT::EventResult |
Optional result of the event to send to the kernel. Some events like Close() do not have a response.
| ULONG PDOKAN_IO_EVENT::EventResultSize |
Size of the EventResult buffer to send to the kernel
| PDOKAN_IO_BATCH PDOKAN_IO_EVENT::IoBatch |
The io batch that owns the lifetime of the EventContext. When it is free, the EventContext of this IoEvent is no longer safe to access.
| BOOL PDOKAN_IO_EVENT::PoolAllocated |
Whether if EventResult was allocated from the memory pool. Large events like FindFiles will allocate a specific buffer that will not come from the memory pool.
The documentation for this struct was generated from the following file:
