Getting the Current Header-Data Split Configuration

To get the current header-data split settings of a miniport adapter, overlying drivers or user-mode applications can query the OID_GEN_HD_SPLIT_CURRENT_CONFIG OID. However, overlying drivers should use the information that NDIS provides to them during initialization and with status indications.

A system administrator can use the GUID that is associated with the OID_GEN_HD_SPLIT_CURRENT_CONFIG OID through the WMI interface. For more information about header-data split WMI GUIDs, see WMI Support for Header-Data Split.

NDIS handles OID_GEN_HD_SPLIT_CURRENT_CONFIG on behalf of the miniport driver. NDIS maintains the current header-data split configuration information based on the miniport driver initialization attributes and the NDIS_STATUS_HD_SPLIT_CURRENT_CONFIG status indication.

The InformationBuffer member of the NDIS_OID_REQUEST structure contains an NDIS_HD_SPLIT_CURRENT_CONFIG structure. NDIS also provides the NDIS_HD_SPLIT_CURRENT_CONFIG structure to overlying drivers during initialization and with the status indication.

When a miniport driver receives an OID_GEN_HD_SPLIT_PARAMETERS set request, the driver must use the contents of the NDIS_HD_SPLIT_PARAMETERS structure to update the current configuration of the miniport adapter. After the update, the miniport driver must report the changes with the NDIS_STATUS_HD_SPLIT_CURRENT_CONFIG status indication. The status indication ensures that all of the overlying drivers are updated with the new information.

When NDIS calls the ProtocolBindAdapterEx function of NDIS 6.1 or later protocol drivers, NDIS provides an NDIS_BIND_PARAMETERS structure with a pointer to an NDIS_HD_SPLIT_CURRENT_CONFIG structure.

When NDIS calls the FilterAttach function of NDIS 6.1 or later filter drivers, NDIS provides an NDIS_FILTER_ATTACH_PARAMETERS structure with a pointer to an NDIS_HD_SPLIT_CURRENT_CONFIG structure.

 

 

Send comments about this topic to Microsoft

Show:
© 2015 Microsoft