Developer Guide

Contents

Guidelines for Designing Pipes

Consider the following best practices when designing pipes:
  • Determine whether you should split the design into multiple kernels connected by pipes.
  • Aggregate data on pipes only when all the data is used at the same point in the kernel.
  • Do not use non-blocking pipes if you are using a looping structure waiting for the data, that is, avoid the following coding pattern for non-blocking pipe accessors:
bool success = false; while (!success) { my_pipe::write(rd_src_buf[i], success); // can be a non-blocking read too }
Whenever you use the above code pattern, use the corresponding blocking accessor instead because it is more efficient in hardware.

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804