Visible to Intel only — GUID: pcq1565976976821
Ixiasoft
Product Discontinuance Notification
1. Introduction to Intel® FPGA SDK for OpenCL™ Pro Edition Best Practices Guide
2. Reviewing Your Kernel's report.html File
3. OpenCL Kernel Design Concepts
4. OpenCL Kernel Design Best Practices
5. Profiling Your Kernel to Identify Performance Bottlenecks
6. Strategies for Improving Single Work-Item Kernel Performance
7. Strategies for Improving NDRange Kernel Data Processing Efficiency
8. Strategies for Improving Memory Access Efficiency
9. Strategies for Optimizing FPGA Area Usage
10. Strategies for Optimizing Intel® Stratix® 10 OpenCL Designs
11. Strategies for Improving Performance in Your Host Application
12. Intel® FPGA SDK for OpenCL™ Pro Edition Best Practices Guide Archives
A. Document Revision History for the Intel® FPGA SDK for OpenCL™ Pro Edition Best Practices Guide
2.1. High-Level Design Report Layout
2.2. Reviewing the Summary Report
2.3. Viewing Throughput Bottlenecks in the Design
2.4. Using Views
2.5. Analyzing Throughput
2.6. Reviewing Area Information
2.7. Optimizing an OpenCL Design Example Based on Information in the HTML Report
2.8. Accessing HLD FPGA Reports in JSON Format
4.1. Transferring Data Via Intel® FPGA SDK for OpenCL™ Channels or OpenCL Pipes
4.2. Unrolling Loops
4.3. Optimizing Floating-Point Operations
4.4. Allocating Aligned Memory
4.5. Aligning a Struct with or without Padding
4.6. Maintaining Similar Structures for Vector Type Elements
4.7. Avoiding Pointer Aliasing
4.8. Avoid Expensive Functions
4.9. Avoiding Work-Item ID-Dependent Backward Branching
5.1. Best Practices for Profiling Your Kernel
5.2. Instrumenting the Kernel Pipeline with Performance Counters (-profile)
5.3. Obtaining Profiling Data During Runtime
5.4. Reducing Area Resource Use While Profiling
5.5. Temporal Performance Collection
5.6. Performance Data Types
5.7. Interpreting the Profiling Information
5.8. Profiler Analyses of Example OpenCL Design Scenarios
5.9. Intel® FPGA Dynamic Profiler for OpenCL™ Limitations
8.1. General Guidelines on Optimizing Memory Accesses
8.2. Optimize Global Memory Accesses
8.3. Performing Kernel Computations Using Constant, Local or Private Memory
8.4. Improving Kernel Performance by Banking the Local Memory
8.5. Optimizing Accesses to Local Memory by Controlling the Memory Replication Factor
8.6. Minimizing the Memory Dependencies for Loop Pipelining
8.7. Static Memory Coalescing
Visible to Intel only — GUID: pcq1565976976821
Ixiasoft
3.6.3. Controlling the Load-Store Units
The Intel® FPGA SDK for OpenCL™ Offline Compiler allows you to control the type of LSU that is being generated for global memory accesses via a set of built-in calls that you can use for loading from and storing to global memory.
Load Built-ins
The variations of the load built-in are summarized in the following table:
Built-in | LSU Type Implemented |
---|---|
__pipelined_load() | Pipelined if possible |
__prefetching_load() | Prefetching if possible |
__burst_coalesced_load() | Burst-coalesced |
__burst_coalesced_cached_load() | Burst-coalesced cached if possible |
All variations expect the following arguments:
Built-in | Type | Description |
---|---|---|
Argument #1 | Pointer | Memory location to load from. |
Argument #2 | Integer |
|
Return value | Object |
|
Store Built-ins
The variations of the store built-in are summarized in the following table:
Built-in | LSU Type Implemented |
---|---|
__pipelined_store() | Pipelined if possible |
__burst_coalesced_store() | Burst-coalesced |
All variations expect the following arguments:
Built-in | Type | Description |
---|---|---|
Argument #1 | Pointer | Memory location to store to. |
Argument #2 | Same as the pointer's base type | Value to be stored. |
Note: All variations of the store built-in are non-value-returning.
Example
Following is an OpenCL example depicting different variations of the load and the store built-ins:
kernel void oclTest(global int * restrict in,
global int * restrict out) {
int i = get_global_id(0);
int a1 = __pipelined_load(in + 3*i+0); // Uses a pipelined LSU
// Uses a burst-coalesced LSU with a cache of size 1024 bytes
int a2 = __burst_coalesced_cached_load(&in[3*i+1], 1024);
int a3 = __prefetching_load(&in[3*i+2]); // Uses a prefetching LSU
__burst_coalesced_store(&out[3*i+0], a3); // Uses a burst-coalesced LSU
}
Note:
- The compiler does not allow you to select an LSU that may cause functionally incorrect results in the context in which it is being requested. For example, if you request a prefetching LSU on a volatile pointer, the compiler errors out. The compiler also errors out if caching is requested in a situation where the cache (which is local to the LSU) may become incoherent due to other LSUs writing to memory.
- The prefetching LSU is not available on the Intel® Stratix® 10 device.