Matrix of NL2 (RTNL2) Functions

This smatrix summarizes the Real-Time API (Rtnl2) function set supported by the wRTOS Network Link Layer (NL2). To support these functions, an application must include the Rtnl2Api.h header files and link in the library Rtnl2Api.lib.

NL2 function name

Shutdown-safe? (No if blank)

Deterministic? (No if blank)

Rtnl2AcquirePhysicalRxQueue

 

 

Rtnl2AcquirePhysicalTxQueue

 

 

Rtnl2AddEtherTypeDispatchRule

 

 

Rtnl2AddUdpPortDispatchRule

 

 

Rtnl2CloseInterface

 

 

Rtnl2CreateLinkStatusChangeEvent

 

 

Rtnl2CreateLogicalRxQueue

 

 

Rtnl2CreateLogicalTxQueue

 

 

Rtnl2CreatePhysicalRxQueueEvent

 

 

Rtnl2CreatePhysicalTxQueueEvent

 

 

Rtnl2DeleteEtherTypeDispatchRule

 

 

Rtnl2DeleteUdpPortDispatchRule

 

 

Rtnl2DestroyLinkStatusChangeEvent

 

 

Rtnl2DestroyLogicalRxQueue

 

 

Rtnl2DestroyLogicalTxQueue

 

 

Rtnl2DestroyPhysicalRxQueueEvent

 

 

Rtnl2DestroyPhysicalTxQueueEvent

 

 

Rtnl2EnableLogicalRxQueueTimestamping

 

 

Rtnl2EnableLogicalTxQueueTimestamping

 

 

Rtnl2EnablePhysicalRxQueueTimestamping

 

 

Rtnl2EnablePhysicalTxQueueTimestamping

 

 

Rtnl2EnumInterface

 

 

Rtnl2ExtractFromPhysicalRxQueue

Yes

Yes, if the Physical Receive Queue was acquired with the RTNL2_PHYSICAL_RX_QUEUE_FLAG_NO_SERIALIZE flag and the underlying driver supports deterministic receive operations. No otherwise.

Please refer to your driver’s documentation to determine whether it supports deterministic receive operations.

Rtnl2ExtractFromPhysicalTxQueue

Yes

Yes, if the Physical Transmit Queue was acquired with the RTNL2_PHYSICAL_TX_QUEUE_FLAG_NO_SERIALIZE flag and the underlying driver supports deterministic transmit operations. No otherwise.

Please refer to your driver’s documentation to determine whether it supports deterministic transmit operations.

Rtnl2GetComponentStatus

 

 

Rtnl2GetEtherTypeDispatchRules

 

 

Rtnl2GetInterfaceConfig

 

 

Rtnl2GetInterfaceFeatures

 

 

Rtnl2GetLinkStatus

 

 

Rtnl2GetLogicalRxQueueMode

 

 

Rtnl2GetLogicalTxQueueTimestamp

Yes

 

Rtnl2GetMacAddress

 

 

Rtnl2GetMsixMessageConfig

 

 

Rtnl2GetPhysicalRxQueueConfig

 

 

Rtnl2GetPhysicalRxQueueMode

 

 

Rtnl2GetPhysicalTxQueueBuffers

 

 

Rtnl2GetPhysicalTxQueueConfig

 

 

Rtnl2GetPhysicalTxQueueTimestamp

Yes

Yes, if the Physical Transmit Queue was acquired with the RTNL2_PHYSICAL_TX_QUEUE_FLAG_NO_SERIALIZE flag. No otherwise.

Rtnl2GetUdpPortDispatchRules

 

 

Rtnl2Init

 

 

Rtnl2IsComponentLicensed

 

 

Rtnl2OpenInterface

 

 

Rtnl2ReceiveFromLogicalRxQueue

Yes

 

Rtnl2ReleasePhysicalRxQueue

 

 

Rtnl2ReleasePhysicalTxQueue

 

 

Rtnl2ReturnPhysicalTxQueueBuffers

 

 

Rtnl2SetInterruptModeration

 

 

Rtnl2SetLogicalRxQueueEtherTypeFilter

 

 

Rtnl2SetLogicalRxQueueMode

 

 

Rtnl2SetLogicalRxQueueMulticastFilter

 

 

Rtnl2SetPhysicalRxQueueMode

 

 

Rtnl2SetPhysicalRxQueueMulticastFilter

 

 

Rtnl2StartComponent

 

 

Rtnl2StartLogicalRxQueue

 

 

Rtnl2StopComponent

 

 

Rtnl2StopLogicalRxQueue

 

 

Rtnl2SubmitToPhysicalRxQueue

Yes

Yes, if the Physical Receive Queue was acquired with the RTNL2_PHYSICAL_RX_QUEUE_FLAG_NO_SERIALIZE flag and the underlying driver supports deterministic receive operations. No otherwise.

Please refer to your driver’s documentation to determine whether it supports deterministic receive operations.

Rtnl2SubmitToPhysicalTxQueue

Yes

Yes, if the Physical Transmit Queue was acquired with the RTNL2_PHYSICAL_TX_QUEUE_FLAG_NO_SERIALIZE flag and the underlying driver supports deterministic transmit operations. No otherwise.

Please refer to your driver’s documentation to determine whether it supports deterministic transmit operations.

Rtnl2TransmitOverLogicalTxQueue

Yes

 

See Also: