cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

rahulgarg
Adept II

rv770 White Paper

Micah: Thanks for the link.

0 Likes
alexaverbuch
Journeyman III

rv770 White Paper

I don't need detailed information, just basic explanations to my questions would be great, and I'm sure the AMD employees could answer these questions easily...

Anybody?

0 Likes
alexaverbuch
Journeyman III

rv770 White Paper

From another thread...

Originally posted by: n0thing ATI's current OpenCL implementation is only for the CPU and caching is automatic from the main memory, so everything is cached I guess except for texture buffers as the textures are not supported in CPU's implementation [ requires Fixed function logic like texture units and samplers ]

For the GPU implementation here are my predictions:

1. Texture Cache : There is a texture cache per SIMD unit, 8kb I think(on rv770). Texture caches are optimized for spatial coherence in texture fetches so you don't need to coalesce as it is automatically done by the tiled rasterization order (fetching a quad of texels) of textures. 

2. Local memory on rv770(LDS) is 16KB per SIMD unit, (R800 should be 32kb as it should support DX11). This memory is configured with 4 banks, each with 256 entries of 16 bytes. So you can read upto 4 aligned 32 bit words in 1 read access from the LDS. Writes have no bank conflicts as each thread can only write to its private location, hence the LDS is not as generic as shared memory specified by OpenCL specification. R800 should support OpenCL's shared memory.

3. Constant cache is 64KB, no idea about coalescing.

4. OpenCL specification says : Reads and writes to global memory may be cached depending on the capabilities of the device.

Here is what OpenCL specification says about constant address space :

The __constant or constant address space name is used to describe variables allocated in global memory and which are accessed inside a kernel(s) as read-only variables.  These read-only variables can be accessed by all (global) work-items of the kernel during its execution.  This qualifier can be used with arguments to functions (including __kernel functions) that are declared as pointers, or with local variables inside a function declared as pointers, or with global variables.  Global variables declared in the program source with the __constant qualifier are required to be initialized.

0 Likes