# TeraScale (microarchitecture)

TeraScale is the codename for a family of graphics processing unit microarchitectures developed by ATI Technologies/AMD and their second microarchitecture implementing the unified shader model following Xenos. TeraScale replaced the old fixed-pipeline microarchitectures and competed directly with Nvidia's first unified shader microarchitecture named Tesla.
TeraScale was used in Radeon HD 2000 manufactured in 80 nm and 65 nm, Radeon HD 3000 manufactured in 65 nm and 55 nm, Radeon HD 4000 manufactured in 55 nm and 40 nm, Radeon HD 5000 and Radeon HD 6000 manufactured in 40 nm. TeraScale was also used in the AMD Accelerated Processing Units code-named "Brazos", "Llano", "Trinity" and "Richland". TeraScale is even found in some of the succeeding graphics cards brands.
TeraScale is a VLIW SIMD architecture, while Tesla is a RISC SIMD architecture, similar to TeraScale's successor Graphics Core Next. TeraScale implements HyperZ.
An LLVM code generator (i.e. a compiler back-end) is available for TeraScale, but it seems to be missing in LLVM's matrix. E.g. Mesa 3D makes use of it.

## TeraScale 1 (VLIW)

At SIGGRAPH 08 in December 2008, AMD employee Mike Houston described some of the TeraScale microarchitecture.
At FOSDEM09 Matthias Hopf from AMDs technology partner SUSE Linux presented a slide regarding the programming of open-source driver for the R600.

### Unified shaders

Previous GPU architectures implemented fixed-pipelines, i.e. there were distinct shader processors for each type of shader. TeraScale leverages many flexible shader processors which can be scheduled to process a variety of shader types, thereby significantly increasing GPU throughput (dependent on application instruction mix as noted below). The R600 core processes vertex, geometry, and pixel shaders as outlined by the Direct3D 10.0 specification for Shader Model 4.0 in addition to full OpenGL 3.0 support.
The new unified shader functionality is based upon a very long instruction word (VLIW) architecture in which the core executes operations in parallel.
A shader cluster is organized into 5 stream processing units. Each stream processing unit can retire a finished single precision floating point MAD (or ADD or MUL) instruction per clock, dot product (DP, and special cased by combining ALUs), and integer ADD. The 5th unit is more complex and can additionally handle special transcendental functions such as sine and cosine. Each shader cluster can execute 6 instructions per clock cycle (peak), consisting of 5 shading instructions plus 1 branch.
Notably, the VLIW architecture brings with it some classic challenges inherent to VLIW designs, namely that of maintaining optimal instruction flow. Additionally, the chip cannot co-issue instructions when one is dependent on the results of the other. Performance of the GPU is highly dependent on the mixture of instructions being used by the application and how well the real-time compiler in the driver can organize said instructions.
R600 core includes 64 shader clusters, while RV610 and RV630 cores have 8 and 24 shader clusters respectively.

### Hardware tessellation

TeraScale includes multiple units capable of carrying out tessellation. Those are similar to the programmable units of the Xenos GPU which is used in the Xbox 360.
Tessellation was officially specified in the major API's starting with DirectX 11 and OpenGL 4. TeraScale 1 based GPU's (HD 2000, 3000 and 4000 series) are only conformant to Direct3D 10 and OpenGL 3.3 and implements therefore a different tessellation principle which uses vendor specific API extensions. The TeraScale 2 based GPU's (starting with the Radeon HD 5000 series) were the first to conform with both Direct3D 11 and OpenGL 4.0 tesselation technique. Although the TeraScale 1 tessellator is simpler in design, it is described by AMD as a subset of the later tesselation standard.
The TeraScale tessellator units allow the developers to take a simple polygon mesh and subdivide it using a curved surface evaluation function. There are different tessellation forms, such as Bézier surfaces with N-patches, B-splines and NURBS, and also some subdivision techniques of the surface, which usually includes displacement map some kind of a texture. Essentially, this allows a simple, low-polygon model to be increased dramatically in polygon density in real-time with very small impact on the performance. Scott Wasson of Tech Report noted during an AMD demo that the resulting model was so dense with millions of polygons that it appeared to be solid.
The TeraScale tessellator is reminiscent of ATI TruForm, the brand name of an early hardware tessellation unit used initially in the Radeon 8500.
ATI TruForm received little attention from software developers. A few games (such as Madden NFL 2004, Serious Sam, Unreal Tournament 2003 and 2004, and unofficially Morrowind), had the support for the ATI's tesselation technology included. Such a slow adaptation has to do with the fact that it was not a feature shared with NVIDIA GPUs, since those had implemented a competing tessellation solution using Quintic-RT patches which had achieved even less support from the major game developers. Since the Xbox 360's GPU is based on the ATI's architecture, Microsoft saw the hardware-accelerated surface tessellation as a major GPU feature. A couple of years later the tesselation feature became mandatory with the release of the DirectX 11 in 2009.
While the tessellation principle introduced with TeraScale was not part of the OpenGL 3.3 or Direct3D 10.0 requirements, and competitors such as the GeForce 8 series lacked similar hardware, Microsoft has added the tessellation feature as part of their DirectX 10.1 future plans. Finally, Microsoft introduced tessellation as a required capability not with DirectX 10.1 but DirectX 11.
GCN geometric processor is AMD's (which acquired the ATI's GPU business) most current solution for carrying out tessellation using the GPU.

### Ultra-threaded dispatch processor

Although the R600 is a significant departure from previous designs, it still shares many features with its predecessor, the Radeon R520. The Ultra-Threaded Dispatch Processor is a major architectural component of the R600 core, just as it was with the Radeon X1000 GPUs. This processor manages a large number of in-flight threads of three distinct types (vertex, geometry, and pixel shaders) and switches amongst them as needed. With a large number of threads being managed simultaneously it is possible to reorganize thread order to optimally utilize the shaders. In other words, the dispatch processor evaluates what goes in the other parts of the R600 and attempts to keep processing efficiency as high as possible. There are lower levels of management as well; each SIMD array of 80 stream processors has its own sequencer and arbiter. The arbiter decides which thread to process next, while the sequencer attempts to reorder instructions for best possible performance within each thread.

### Texturing and anti-aliasing

Texturing and final output aboard the R600 core is similar but also distinct from R580. R600 is equipped with 4 texture units that are decoupled (independent) from the shader core, like in the R520 and R580 GPUs. The render output units (ROPs) of Radeon HD 2000 series now performs the task of Multisample anti-aliasing (MSAA) with programmable sample grids and maximum of 8 sample points, instead of using pixel shaders as in the Radeon X1000 series. Also new is the capability to filter FP16 textures, popular with HDR lighting, at full-speed. ROP can also perform trilinear and anisotropic filtering on all texture formats. On R600, this totals 16 pixels per clock for FP16 textures, while higher precision FP32 textures filter at half-speed (8 pixels per clock).
Anti-aliasing capabilities are more robust on R600 than on the R520 series. In addition to the ability to perform 8× MSAA, up from 6× MSAA on the R300 through R580, R600 has a new custom filter anti-aliasing (CFAA) mode. CFAA refers to an implementation of non-box filters that look at pixels around the particular pixel being processed in order to calculate the final color and anti-alias the image. CFAA is performed by shader, instead of in the ROPs. This brings greatly enhanced programmability because the filters can be customized, but may also bring potential performance issues because of the use of shader resources. As of launch of R600, CFAA utilizes wide and narrow tent filters. With these, samples from outside the pixel being processed are weighted linearly based upon their distance from the centroid of that pixel, with the linear function adjusted based on the wide or narrow filter chosen.

### Memory controllers

Memory controllers are connected via internal bi-directional ring bus wrapped around the processor. In Radeon HD 2900, it is a 1,024-bit bi-directional ring bus (512-bit read and 512-bit write), with 8 64-bit memory channels for a total bus width of 512-bits on the 2900 XT.; in Radeon HD 3800, it is a 512-bit ring bus; in Radeon HD 2600 and HD 3600, it is a 256-bit ring bus; In Radeon HD 2400 and HD 3400, there is no ring bus.

### Half-generation update

The series saw a half-generation update with die shrink (55 nm) variants: RV670, RV635 and RV620. All variants support PCI Express 2.0, DirectX 10.1 with Shader Model 4.1 features, dedicated ATI Unified Video Decoder (UVD) for all models and PowerPlay technology for desktop video cards.
Except the Radeon HD 3800 series, all variants supported 2 integrated DisplayPort outputs, supporting 24- and 30-bit displays for resolutions up to 2,560×1,600. Each output included 1, 2, or 4 lanes per output, with data rate up to 2.7 Gbit/s per lane.
ATI claimed that the support of DirectX 10.1 can bring improved performance and processing efficiency with reduced rounding error (0.5 ULP compared with average error 1.0 ULP as tolerable error), better image details and quality, global illumination (a technique used in animated films, and more improvements to consumer gaming systems therefore giving more realistic gaming experience. )

### Video cards

* Radeon HD 2000 series
* Radeon HD 3000 series
* Radeon HD 4000 series
(see list of chips in those pages)

## TeraScale 2 (VLIW5)

TeraScale 2 (VLIW5) was introduced with Radeon HD 5000 series GPUs in "Evergreen" generation.
At HPG10 Mark Fowler presented the "Evergreen" and stated that e.g. 5870 (Cypress), 5770 (Juniper) and 5670 (Redwood) support max resolution of the 6 times 2560×1600 pixels, while the 5470 (Cedar) supports 4 times 2560×1600 pixels, important for AMD Eyefinity multi-monitor support.
With the release of Cypress, the Terascale graphics engine architecture has been upgraded with twice the number of stream cores, texture units and ROP units compared to the RV770. The architecture of stream cores is largely unchanged, but adds support for DirectX 11/DirectCompute 11 capabilities with new instructions. Also similar to RV770, four texture units are tied to 16 stream cores (each have five processing elements, making a total of 80 processing elements). This combination of is referred to as a SIMD core.
Unlike the predecessor Radeon R700, as DirectX 11 mandates full developer control over interpolation, dedicated interpolators were removed, relying instead on the SIMD cores. The stream cores can handle the higher rounding precision fused multiply–add (FMA) instruction in both single and double precision which increases precision over multiply–add (MAD) and is compliant to IEEE 754-2008 standard. The instruction sum of absolute differences (SAD) has been natively added to the processors. This instruction can be used to greatly improve the performance of some processes, such as video encoding and transcoding on the 3D engine. Each SIMD core is equipped with 32 KiB local data share and 8 kiB of L1 cache, while all SIMD cores share 64 KiB global data share.

### Memory controller

Each memory controller ties to two quad ROPs, one per 64-bit channel, and dedicated 512 KiB L2 cache.

### Power saving

AMD PowerPlay is supported, see there.

### Chips

* Evergreen chips:
** Cedar RV810
** Cypress RV870
** Hemlock R800
** Juniper RV840
** Redwood RV830
* Northern Islands chips:
** Barts RV940
** Caicos RV910
** Turks RV930
* APU that include a TeraScale 2 IGP:
** Llano
** Ontario
** Zacate

## TeraScale 3 (VLIW4)

TeraScale 3 (VLIW4) replaces the previous 5-way VLIW designs with a 4-way VLIW design. The new design also incorporates an additional tessellation unit to improve Direct3D 11 performance.
TeraScale 3 is introduced in the Radeon HD 6900-branded graphics cards and also implemented in the Trinity and Richland APUs.

### Power saving

AMD PowerTune, dynamic frequency scaling for GPUs, was introduced with the Radeon HD 6900 series on December 15, 2010 and has seen continued development, as documented in some reviews by AnandTech.

### Chips

* Northern Islands chips:
** Cayman RV970
** Antilles R900
** Trinity and Richland include a TeraScale 3 IGP

## Successor

At HPG11 in August 2011 AMD employees Michael Mantor (Senior Fellow Architect) and Mike Houston (Fellow Architect) presented Graphics Core Next, the microarchitecture succeeding TeraScale.

## Comparison of TeraScale chips

| Microarchitecture | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 1 | TeraScale 2 | TeraScale 2 | TeraScale 2 | TeraScale 2 | TeraScale 2 | TeraScale 2 | TeraScale 2 | TeraScale 3 |
| Chip$^1$ | R600 | RV610 | RV620 | RV630 | RV635 | RV670 | RV710 | RV711 | RV730 | RV740 | RV770 | RV790 | Cedar (RV810) | Redwood (RV830) | Juniper (RV840) | Cypress (RV870) | Caicos (RV910) | Turks (RV930) | Barts (RV940) | Cayman (RV970) |
| Code name | Pele | Laka | Koopa | Shaka | Wario | Boom | Luigi | Luigi | Mario | Walden | Wekiva | Spartan | ? | ? | ? | ? | ? | ? | Victoria | ? |
| Chip variant(s) | — | M72 M74 | M82 | M76 | M86 | M88 | M92 | M93 | M96 | M97 | M98 | — | Park Robson | Capilano Madison Pinewood | Broadway Granville | Hemlock Lexington | Seymour | Onega Thames Whistler | Blackcomb | Antilles |
| Fab (nm) | 80 | 65 | 55 | 65 | 55 | 55 | 55 | 55 | 55 | 40 | 55 | 55 | 40 | 40 | 40 | 40 | 40 | 40 | 40 | 40 |
| Die size (mm$^2$) | 420 | 85 / 82 (M74) | 67 | 153 | 135 | 192 | 73 | 73 | 146 | 137 | 256 | 282 | 59 | 104 | 166 | 334 | 67 | 118 / 104 (Thames, Whistler) | 255 / 212 (Blackcomb) | 389 |
| Transistors (million) | 720 | 180 | 181 | 390 | 378 | 666 | 242 | 242 | 514 | 826 | 956 | 959 | 292 | 627 | 1,040 | 2,154 | 370 | 716 | 1,700 | 2,640 |
| Transistor density (MTr/mm$^2$) | 1.7 | 2.1 / 2.2 (M74) | 2.7 | 2.5 | 2.8 | 3.5 | 3.3 | 3.3 | 3.5 | 6.0 | 3.7 | 3.4 | 4.9 | 6.0 | 6.3 | 6.4 | 5.5 | 6.1 / 6.9 (Thames, Whistler) | 6.7 / 8.0 (Blackcomb) | 6.8 |
| Compute units | 4 | 2 | 2 | 3 | 3 | 4 | 1 | 1 | 4 | 8 | 10 | 10 | 2 | 5 | 10 | 20 / 5 (Lexington) | 2 | 6 | 14 | 24 |
| Thread processors | 16 | 4 | 4 | 8 | 8 | 16 | 8 | 8 | 32 | 32 | 40 | 40 | 8 | 20 | 40 | 80 / 20 (Lexington) | 8 | 24 | 56 | 96 |
| Stream processors | 320 | 40 | 40 | 120 | 120 | 320 | 80 | 80 | 320 | 640 | 800 | 800 | 80 | 400 | 800 | 1600 / 400 (Lexington) | 160 | 480 | 1120 | 1536 |
| Texture mapping units | 16 | 4 | 4 | 8 | 8 | 16 | 8 | 8 | 32 | 32 | 40 | 40 | 8 | 20 | 40 | 80 / 20 (Lexington) | 8 | 24 | 56 | 96 |
| Render output units | 16 | 4 | 4 | 4 | 4 | 16 | 4 | 4 | 8 | 16 | 16 | 16 | 4 | 8 | 16 | 32 / 8 (Lexington) | 4 | 8 | 32 | 32 |
| Z/Stencil OPS | 32 | 8 | 8 | 8 | 8 | 32 | 4 | 4 | 32 | 64 | 64 | 64 | 4 | 40 | 40 | 40 | 16 | 32 | 40 | 128 |
| L1 cache (KB) | 32 per 4 SPs (Stream processors) | 32 per 4 SPs (Stream processors) | 32 per 4 SPs (Stream processors) | 32 per 4 SPs (Stream processors) | 32 per 4 SPs (Stream processors) | 32 per 4 SPs (Stream processors) | 16 per CU (Compute unit) | 16 per CU (Compute unit) | 16 per CU (Compute unit) | 16 per CU (Compute unit) | 16 per CU (Compute unit) | 16 per CU (Compute unit) | 8 per CU | 8 per CU | 8 per CU | 8 per CU | 8 per CU | 8 per CU | 8 per CU | 8 per CU |
| L2 cache (KB) | 256 | 32 | 64 | 64 | 128 | 256 | 64 | 64 | 128 | 128 | 256 | 256 | 128 | 256 | 256 | 512 / 256 (Lexington) | 128 | 256 | 512 | 512 |
| Display Core Engine | 2.0 | 2.0 | 3.0 | 2.0 | 3.0 | 2.0 | 3.2 | 3.2 | 3.2 | 3.2 | 3.1 | 3.1 | 4.0 | 4.0 | 4.0 | 4.0 | 5.0 | 5.0 | 5.0 | 5.0 |
| Unified Video Decoder | Avivo HD | 1.0 | 1.0 | 1.0 | 1.0 | 1.0 | 2.2 | 2.2 | 2.2 | 2.2 | 2.0 | 2.0 | 2.3 | 2.3 | 2.3 | 2.3 | 3.1 | 3.1 | 3.1 | 3.1 |
| Initial launch | May 2007 | Jan 2007 | Jan 2008 | Jun 2007 | Jan 2008 | Nov 2007 | Sep 2008 | May 2010 | Sep 2008 | Apr 2009 | Jun 2008 | Apr 2009 | Feb 2010 | Jan 2010 | Oct 2009 | Sep 2009 | Feb 2011 | Feb 2011 | Oct 2010 | Dec 2010 |
| Series | R600 (Radeon HD 2000 / Radeon HD 3000) | R600 (Radeon HD 2000 / Radeon HD 3000) | R600 (Radeon HD 2000 / Radeon HD 3000) | R600 (Radeon HD 2000 / Radeon HD 3000) | R600 (Radeon HD 2000 / Radeon HD 3000) | R600 (Radeon HD 2000 / Radeon HD 3000) | R700 (Radeon HD 4000) | R700 (Radeon HD 4000) | R700 (Radeon HD 4000) | R700 (Radeon HD 4000) | R700 (Radeon HD 4000) | R700 (Radeon HD 4000) | Evergreen (Radeon HD 5000) | Evergreen (Radeon HD 5000) | Evergreen (Radeon HD 5000) | Evergreen (Radeon HD 5000) | Northern Islands (Radeon HD 6000) | Northern Islands (Radeon HD 6000) | Northern Islands (Radeon HD 6000) | Northern Islands (Radeon HD 6000) |
| References | | [32][33] [34][35] | [36][37] [38] | [39][40] [41] | [42][43] [44] | [45][46] [47] | [48][49] [50] | [51] [52] | [53][54] [55] | [56][57] [58] | [59][60] [61] | | [64][65] [66][67] | [68][69] [70][71][72] | [73] [74][75] | [76][77] [78][79] | [80][81] [82] | [83][84] [85][86][87] | [88][89] [90] | [91][92] [93] |
$^1$ Duo chips such as R680 (2x RV670) and R700 (2x RV770) are not listed.