Hi @aneesullah,

I'm going to reply that I think this might depend on how the code going into HLS is written.

Vivado HLS's user guide UG902 describes a long list of some example designs on pg. 68:
https://www.xilinx.com/support/documentation/sw_manuals/xilinx2020_1/ug902-vivado-high-level-synthesis.pdf

Some of these examples have specific interfaces:

• axi_lite
• axi_master
• axi_stream_no_side_channel_data
• axi_stream_side_channel_data
  ...

If we were to try to characterize the packet interfaces used in OpenNIC, I think they are like AXI4-stream with custom side-channel data (e.g. multiple custom TUSER like signals in OpenNIC).

I think as long as the interfaces are capable of transmitting the necessary information and the function has acceptable performance (e.g. initiation interval), then perhaps this might not be an issue.

Best regards,
--Chris

Thanks a lot Chris for your reply. Yes, I am using the axi stream with custom side band channels and I am able to generate the interfaces correctly. What is an acceptable Initiation Interval (II) for functions that drops inside the 250 Mhz user logic box?
Regards,
Anees

Hi @aneesullah, I think this would depend on your use case for the smart nic, and whether your HLS block is a part of the main datapath. I would aim for an initiation interval of 1 if possible. I think that the worst case is processing sustained bursts of 65 byte frames at 100 Gbps, for a packet rate of 150 Mpps. If your packet rate won't get that high, then you probably do not need to worry about this.