NET_ADAPTER_RX_CAPABILITIES_INIT_SYSTEM_MANAGED - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// netadapter.h
void NET_ADAPTER_RX_CAPABILITIES_INIT_SYSTEM_MANAGED(
[_Out_] NET_ADAPTER_RX_CAPABILITIES *RxCapabilities,
[_In_] SIZE_T MaximumFrameSize,
[_In_] SIZE_T MaximumNumberOfQueues
);
View the official Windows Driver Kit DDI referenceNo description available.
The NET_ADAPTER_RX_CAPABILITIES_INIT_SYSTEM_MANAGED function initializes a NET_ADAPTER_RX_CAPABILITIES structure for a net adapter that would like to specify operating system-managed receive buffer allocation and attachment, but not the use of DMA memory mapping.
RxCapabilities [_Out_]A pointer to a driver-allocated NET_ADAPTER_RX_CAPABILITIES structure.
MaximumFrameSize [_In_]The maximum frame size, in bytes, that the adapter can receive.
MaximumNumberOfQueues [_In_]The maximum number of receive queues that the adapter supports.
This function is one of three possible functions to call in order to initialize a NET_ADAPTER_RX_CAPABILITIES structure. Which one the client driver should call depends on how it would like to allocate receive buffers and if it would like to use DMA.
The client driver must call NET_ADAPTER_RX_CAPABILITIES_INIT_SYSTEM_MANAGED to initialize its NET_ADAPTER_RX_CAPABILITIES structure if it would like the operating system to perform receive buffer allocation and attachment, but does not require DMA memory mapping. By calling this function, the Rx capabilities structure's AllocationMode member is set to NetRxFragmentBufferAllocationModeSystem and the AttachmentMode member is set to NetRxFragmentBufferAttachmentModeSystem. Because the driver does not specify DMA capabilities in this case, this function also sets the MappingRequirement member to NetMemoryMappingRequirementNone.
NET_ADAPTER_RX_CAPABILITIES_INIT_DRIVER_MANAGED
NET_ADAPTER_RX_CAPABILITIES_INIT_SYSTEM_MANAGED_DMA