Page 1:Steamroller, GCN, HSA, 28 nm: Oh My!
Page 2:Meet The Compute Core
Page 3:A More Capable GPU: GCN Surfaces In Kaveri
Page 4:Enabling HSA On The Kaveri APU
Page 5:Test Hardware And Software
Page 6:Gaming: BioShock Infinite And Grid 2
Page 7:Gaming: The Elder Scrolls V: Skyrim And World Of Warcraft
Page 8:Dual Graphics: Does Kaveri Fix CrossFire's Problems?
Page 9:Results: Synthetics
Page 10:Results: Content Creation
Page 11:Results: Adobe CC
Page 12:Results: Productivity
Page 13:Results: Compression Apps
Page 14:Results: Media Encoding
Page 15:Results: Power Consumption And Efficiency
Page 16:Hoping The Best Is Yet To Come
Enabling HSA On The Kaveri APU
Let’s get back to that concept of integration. Done right, integration should allow for compounding efficiencies. Subsystems brought closer together can communicate more quickly and save power.
Back when AMD introduced its Llano APU, the company put four Stars cores, a northbridge, two 64-bit memory channels, PCIe control, and a graphics engine on one die. It provided a 128-bit Fusion Control Link to the GPU for access to coherent memory space, simultaneously giving the CPU access to the GPU’s frame buffer. Separately, another bus gave the graphics engine higher-bandwidth access to memory.
The advent of Trinity (and then Richland) saw AMD push integration even further. It unified the CPU and graphics northbridges, doubling the data path bandwidth of its Radeon Memory Bus in the process. Perhaps even more significantly, it added an I/O memory management unit, attached through the Fusion Control Link, which gave the GPU access to virtual address space. The road to HSA was slowly being paved.
Kaveri incorporates a second bus through the IOMMU for coherency. It also exposes functionality called system-level atomics for synchronizing work across different cores. Together, those features complete the puzzle and enable a trio of HSA features.
A heterogeneous unified memory architecture, to begin, gives the CPU and GPU subsystems visibility into the entire memory space, up to 32 GB. Additionally, both the CPU and GPU are treated equally by AMD’s heterogeneous queuing model. Work can be dispatched from one to the other and vice versa. As a result, the APU’s on-die resources can tag-team more compute-intensive workloads.
Right off the bat, AMD is identifying a handful of tasks that’ll benefit from greater compute potential in the mobile and desktop spaces. Media playback is the first. You’ve already seen us demonstrate how demanding H.265 encoding can be. AMD is going to offload encode/decode onto the GPU, since it wasn’t able to build a fixed-function accelerator for playback in time, and doesn’t expect to even try encoding that way. Unfortunately, the requisite software is still being worked on, so we can’t compare CPU- to GPU-based HEVC playback today. In the same vein, video and image editing already do lean on GPU resources (we have our own Photoshop, Premiere Pro, and After Effects tests that are technically OpenCL-optimized). This will naturally continue with Kaveri. Of course, gaming is that killer app always able to push the latest and greatest; developers are already using compute in a variety of ways. For example, DICE uses a compute shader for tile-based deferred rendering in Battlefield 4.
How Do I Use This HSA You Speak Of?
AMD makes a big deal about its effort to design hardware that just works within the scope of how developers write code today, rather than forcing them to change direction yet again. Leveraging HSA shouldn't have the long adoption curve of multi-core CPUs, which were difficult to fully utilize, or GPGPU computing, which was only possible through low-level APIs for quite a while. Instead, the company’s HSA features map to OpenCL 2.0, ratified late last year.
The bad news is that the applications already installed on your PC aren’t optimized for Kaveri’s full feature set (though AMD does claim legacy OpenCL benefits from HSA thanks to run-time improvements). That’ll require ISVs to gradually introduce updated software. But a growing swath of developers is becoming increasingly proficient with OpenCL, and we’ve already incorporated a number of workloads into our benchmark suite able to leverage the API. Though testing won’t reflect HSA-oriented design today, we’re already working with a couple of big names to fold in relevant workloads.
Bottom line: we waited years for the first mainstream OpenCL-optimized applications, and now we have many well-known multimedia, content creation, productivity, and gaming titles benefiting from heterogeneous computing. We only expect to be on-hold for months before software starts showing up written for OpenCL 2.0. When that happens, AMD’s HSA features should augment performance and power consumption in different ways.
- Steamroller, GCN, HSA, 28 nm: Oh My!
- Meet The Compute Core
- A More Capable GPU: GCN Surfaces In Kaveri
- Enabling HSA On The Kaveri APU
- Test Hardware And Software
- Gaming: BioShock Infinite And Grid 2
- Gaming: The Elder Scrolls V: Skyrim And World Of Warcraft
- Dual Graphics: Does Kaveri Fix CrossFire's Problems?
- Results: Synthetics
- Results: Content Creation
- Results: Adobe CC
- Results: Productivity
- Results: Compression Apps
- Results: Media Encoding
- Results: Power Consumption And Efficiency
- Hoping The Best Is Yet To Come