Function summary

Interface

Description

Synchronous

• Can allow packet loss and can introduce data overload conditions.

• Adequate for simple applications but not as efficient as asynchronous interfaces.

• Can stall multiple-threaded calling applications until a response is received from the TX host-based driver.

• Does not include a flow control mechanism, causing dropped packets and resource depletion during heavy packet traffic, whether from host to TX board or from TX board to host.

• Used when opening a CPI channel using cpi_open.

Asynchronous

• Recommended for all development because it is more efficient than synchronous interfaces.

• Does not stall the calling application because all responses from the driver are handled as independent events. For certain operating systems, multiple-threaded applications must use an asynchronous interface. For operating systems that do not impose this restriction, an asynchronous interface is still recommended.

• Includes flow control mechanisms to ensure that no packets are dropped and no depletion conditions are introduced due to host traffic.

• Used when opening a CPI channel with cpia_open or cpix_open.