AVStream manages a construct referred to as an object bag for each AVStream object visible to the minidriver. An object bag is a generic container for holding dynamically allocated memory associated with a given object.
Uses of object bags include:
Minidrivers can use object bags for memory management to reduce cleanup work. In order to do this, a minidriver must first call ExAllocatePoolWithTag to allocate dynamic memory and associate it with a given object. The minidriver then adds the allocated memory to the object bag by calling KsAddItemToObjectBag.
When the minidriver calls KsAddItemToObjectBag, AVStream associates a default cleanup function (typically ExFreePool) with the object. Alternatively, the minidriver can include a pointer to a minidriver-provided cleanup routine in the Free parameter of KsAddItemToObjectBag. When an object is closed, AVStream removes every item from the object bag and calls the associated cleanup routines.
Sharing dynamically allocated data among several AVStream objects.
A minidriver can share dynamically allocated data among several AVStream objects by placing a given item in more than one object bag. In this case, AVStream does not release the given item until it is no longer contained in any object bag. The only limitation on the number of items an object bag can contain is available memory.
Determining which structures can be edited with descriptors.
If a minidriver dynamically allocates a descriptor or a descriptor substructure, the minidriver places the descriptor in the relevant object bag. The _KsEdit function then uses this information to determine whether a given structure can be edited.
AVStream automatically removes items from an object bag if the owning object is deleted.
Build date: 12/17/2013