OID_SRIOV_PF_LUID
An overlying driver issues an object identifier (OID) query request of OID_SRIOV_PF_LUID to receive the locally unique identifier (LUID) associated with the PCI Express (PCIe) Physical Function (PF) of the network adapter.
The InformationBuffer member of the NDIS_OID_REQUEST structure contains a pointer to the NDIS_SRIOV_PF_LUID_INFO structure.
Remarks
NDIS generates a LUID for the PF before NDIS calls the MiniportInitializeEx function of the miniport driver for the PF. This LUID is valid until NDIS calls the MiniportHaltEx function of the driver.
Note The value of the Luid member differs from the NetLuid member of the NDIS_MINIPORT_INIT_PARAMETERS structure. This structure is passed to the miniport driver through the MiniportInitParameters parameter of MiniportInitializeEx.
Return Status Codes
NDIS handles the OID query request of OID_SRIOV_PF_LUID request for miniport drivers. The drivers will not be issued this OID request.
When NDIS handles the OID_SRIOV_PF_LUID request, it returns one of the following status codes.
| Status Code | Description |
|---|---|
NDIS_STATUS_SUCCESS |
The OID request completed successfully. |
NDIS_STATUS_NOT_SUPPORTED |
The miniport driver either does not support the single root I/O virtualization (SR-IOV) interface or is not enabled to use the interface. |
NDIS_STATUS_INVALID_LENGTH |
The information buffer was too short. The miniport driver must set the DATA.QUERY_INFORMATION.BytesNeeded member in the NDIS_OID_REQUEST structure to the minimum buffer size that is required. |
NDIS_STATUS_FAILURE |
The request failed for other reasons. |
Requirements
Version |
Supported in NDIS 6.30 and later. |
Header |
Ntddndis.h (include Ndis.h) |
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for