Table of contents
Collapse the table of content
Expand the table of content

Filter Specific Allocators

Last Updated: 8/26/2016

Filters that require allocators for on-board memory or other device dependent storage methods can provide a specific allocator by supporting allocator properties and methods. For more information, see KSPROPERTY_STREAM_ALLOCATOR.

A filter receives an IRP_MJ_CREATE of type KSCREATE_REQUEST_ALLOCATOR specifying the framing options for the allocator. The minidriver's allocator creation routine validates the create request by calling KsValidateAllocatorCreateRequest. If the call is successful, this routine returns a pointer to the relevant KSALLOCATOR_FRAMING structure.

If the filter cannot satisfy the framing requirements, it returns a failure code in response to the IRP. Otherwise, the filter attaches a pointer to a structure to the FsContext member of the file object and services the resulting allocator requests.

If buffers passed to the streaming interface should be modified in-place by the filter, the user-mode client sets the KSALLOCATOR_REQUIREMENTF_INPLACE_MODIFIER flag on the relevant KSALLOCATOR_FRAMING structure.

There are two interfaces available to the allocator. First, all allocators must support the IRP-based KSMETHODSETID_StreamAllocator. Allocators using this mechanism are limited to a maximum number of allocated frames. Requests to allocate frames beyond this limit will be marked pending.

Second, the minidriver can support function table access if the allocation pool type can be serviced at DISPATCH_LEVEL. Providing function table access is optional. Do this by supporting the properties in KSPROPSETID_StreamAllocator.

The DISPATCH_LEVEL interface operates as follows:

When an allocate request is submitted to the allocator, the allocator returns a pointer to a frame if one is available. If not, it immediately returns NULL.

When a free request is submitted to the allocator, the allocator signals the stream allocator "free frame" event notifying the client that a free frame is available. Additionally, if there are allocation request IRPs waiting to be completed, the allocator must schedule a worker item (if the current IRQL is not PASSIVE_LEVEL) and complete the request with the free frame.

It is possible for both the DISPATCH_LEVEL interface and the IRP-based interface to contend for free frames. KS synchronizes this queue using the cancel spin lock.

Send comments about this topic to Microsoft

© 2017 Microsoft