Blocking Pipes (CL)
This is simple example of vector addition to demonstrate OpenCL Pipe Memory usage. OpenCL PIPE memory functionality allows user to achieve kernel-to-kernel data transfer without using global memory.
KEY CONCEPTS: Dataflow, kernel to kernel pipes
KEYWORDS: pipe, xcl_reqd_pipe_depth, read_pipe_block(), write_pipe_block()
SUPPORTED PLATFORMS
| Platform | Board | Software Version |
|---|---|---|
| xilinx_u200_qdma | Xilinx Alveo U200 | SDx 2019.1 |
| xilinx_u50_xdma | Xilinx Alveo U50 | SDx 2019.1 |
| xilinx_u250_qdma | Xilinx Alveo U250 | SDx 2019.1 |
| xilinx_u200_xdma | Xilinx Alveo U200 | SDx 2019.1 |
| xilinx_u280_xdma | Xilinx Alveo U280 | SDx 2019.1 |
| xilinx_u250_xdma | Xilinx Alveo U250 | SDx 2019.1 |
DESIGN FILES
Application code is located in the src directory. Accelerator binary files will be compiled to the xclbin directory. The xclbin directory is required by the Makefile and its contents will be filled during compilation. A listing of all the files in this example is shown below
src/adder.cl
src/host.cpp
COMMAND LINE ARGUMENTS
Once the environment has been configured, the application can be executed by
./host <adder XCLBIN>