As a query request, administrative applications (or possibly overlying drivers) use the OID_TCP_OFFLOAD_CURRENT_CONFIG OID to determine the current task offload configuration settings of an underlying miniport adapter. A system administrator can use this OID through the Microsoft Windows Management Instrumentation (WMI) interface.

Set requests are not supported.


NDIS handles this OID for miniport drivers. Miniport drivers report miniport adapter offload capabilities to NDIS. For information about passing task offload configuration settings to NDIS from a miniport driver and from NDIS to overlying drivers, see NDIS_OFFLOAD.

The InformationBuffer member of the NDIS_OID_REQUEST structure contains an NDIS_OFFLOAD structure. The NDIS_OFFLOAD structure includes the following miniport adapter capabilities:

In response to OID_TCP_OFFLOAD_CURRENT_CONFIG, the Encapsulation members of the structures in the preceding list define the packet encapsulation capabilities of the miniport adapter. NDIS provides a bitwise OR of the flags that are provided in the Encapsulation members of these structures. The other structure members contain settings for various offload services. For more information about encapsulation and other capabilities, see NDIS_TCP_IP_CHECKSUM_OFFLOAD, NDIS_TCP_LARGE_SEND_OFFLOAD_V1, NDIS_IPSEC_OFFLOAD_V1, and NDIS_TCP_LARGE_SEND_OFFLOAD_V2.

Miniport adapters must support Ethernet encapsulation for all of the types of task offload that they support. The other types of encapsulation are optional.

Miniport drivers should automatically enable all of the task offload capabilities during initialization.

See also



Version: Windows Vista and later Header: Ntddndis.h (include Ndis.h)