Cache (computing): Difference between revisions

Content deleted Content added
review: ce for clarity. repos ref. caps. rm acro from heading.
Tag: Reverted
Line 69:
Earlier [[graphics processing unit]]s (GPUs) often had limited read-only [[texture cache]]s and used [[swizzling (computer graphics)|swizzling]] to improve 2D [[locality of reference]]. [[Cache miss]]es would drastically affect performance, e.g. if [[mipmapping]] was not used. Caching was important to leverage 32-bit (and wider) transfers for texture data that was often as little as 4 bits per pixel.
 
As GPUs advanced, supporting [[general-purpose computing on graphics processing units]] and [[compute kernel]]s, they have developed progressively larger and increasingly general cachesCaches, including [[instruction cache]]s for [[shader]]s, exhibiting functionality commonly found in CPU caches. These caches have grown to handle [[synchronization primitive]]s between threads and [[atomic operation]]s, and interface with a CPU-style MMU.
 
===DSPs===