Software Migration

Alveo X3522 User Guide (UG1523)

Document ID
Release Date
1.4 English

This section outlines issues you might have when migrating software to the X3522 from its predecessors:

Onload Migration

  • No application changes are required.
  • For best performance, system tuning is likely to need adjustment.
  • A maximum of 15 Onload stacks can be created without sharing CTPIO apertures.
  • You can add interfaces to the allowlist/denylist to avoid an application consuming CTPIO apertures on interfaces where it does not need to accelerate traffic.
  • Onload utilities interact only with components of the Onload package. In particular, the onload_tool utility does not reload the xilinx_efct driver.

See the Onload User Guide (UG1586).

TCPDirect Migration

  • TX-alternatives are not supported.
  • Overlapped receives are not supported.
  • You must ensure PIO is not enabled (i.e. set the attribute pio=0).
  • Dynamically linked applications that do not have any of the preceding issues can be used unchanged.
  • Statically linked applications require re-linking.

See the TCPDirect User Guide (SF-116303-CD).

ef_vi Migration

  • There are new events to receive data, and new calls to retrieve the data.
  • The driver manages the RX buffers, so you do not post descriptors for packet buffers, but must instead release received packets after processing them.
  • TX must use only CTPIO.
  • You must filter in software for unwanted data, including non-UDP/TCP frames.
  • Some example applications do not support the X3522.

See the Alveo X3 ef_vi Conversion Guide (XN-201257-CD) and the ef_vi User Guide (SF-114063-CD).

sfptpd Migration

  • The X3522 needs an updated version of sfptpd that recognizes its new PCIe vendor ID.
  • It will then be treated in the same way as other AMD/Solarflare NICs.
  • No changes are needed to configuration.

See the Enhanced PTP User Guide (UG1602).