Cache control instruction

<h2 id="examples">Examples</h2>
<p>Several such instructions, with variants, are supported by several processor <a href="/facts/Instruction_set/8p8vwUeE">instruction set</a> architectures, such as <a href="/facts/ARM_architecture/SALsYA79">ARM</a>, <a href="/facts/MIPS_architecture/efV4KgK4">MIPS</a>, <a href="/facts/PowerPC/DqmM9y50">PowerPC</a>, and <a href="/facts/X86/Kypq5fgu">x86</a>.
</p>
<h3>Prefetch</h3>
<p>Also termed <i>data cache block touch</i>, the effect is to request loading the cache line associated with a given address. This is performed by the PREFETCH instruction in the <a href="/facts/X86/Kypq5fgu">x86</a> instruction set. Some variants bypass higher levels of the <a href="/facts/Cache_hierarchy/9lGPQ5r6">cache hierarchy</a>, which is useful in a 'streaming' context for data that is traversed once, rather than held in the working set. The <a href="/facts/Cache_prefetching/cuCGl0Vm">prefetch</a> should occur sufficiently far ahead in time to mitigate the <a href="/facts/Latency_(engineering)/6Bjhn30H">latency</a> of memory access, for example in a loop traversing memory linearly. The <a href="/facts/GNU_Compiler_Collection/t07jh01k">GNU Compiler Collection</a> <a href="/facts/Intrinsic_function/r0re5n09">intrinsic function</a> __builtin_prefetch can be used to invoke this in the programming languages <a href="/facts/C_(programming_language)/Ky2No763">C</a> or <a href="/facts/C%252B%252B/Et0F2qn9">C++</a>.
</p>
<h3>Instruction prefetch</h3>
<p>A variant of prefetch for the instruction cache.
</p>
<h3>Data cache block allocate zero</h3>
<p>This hint is used to prepare cache lines before overwriting the contents completely. In this example, the CPU needn't load anything from <a href="/facts/Main_memory/wPHKFpdx">main memory</a>. The semantic effect is equivalent to an aligned <a href="/facts/Memset/V0AYCYR2">memset</a> of a cache-line sized block to zero, but the operation is effectively free.
</p>
<h3>Data cache block invalidate</h3>
<p>This hint is used to discard cache lines, without committing their contents to main memory. Care is needed since incorrect results are possible. Unlike other cache hints, the semantics of the program are significantly modified. This is used in conjunction with allocate zero for managing temporary data. This saves unneeded main memory bandwidth and cache pollution.
</p>
<h3>Data cache block flush</h3>
<p>This hint requests the immediate eviction of a cache line, making way for future allocations. It is used when it is known that data is no longer part of the <a href="/facts/Working_set/z7HKqFa5">working set</a>.
</p>
<h3>Other hints</h3>
<p>Some processors support a variant of <a href="/facts/Instruction_set/8p8vwUeE">load–store instructions</a> that also imply cache hints. An example is load last in the <a href="/facts/PowerPC/DqmM9y50">PowerPC</a> instruction set, which suggests that data will only be used once, i.e., the cache line in question may be pushed to the head of the eviction queue, whilst keeping it in use if still directly needed.
</p>
<h2 id="alternatives">Alternatives</h2>
<h3>Automatic prefetch</h3>
<p>In recent times, cache control instructions have become less popular as increasingly advanced application processor designs from <a href="/facts/Intel/SMF0gJJX">Intel</a> and <a href="/facts/ARM_Holdings/jqqppj7b">ARM</a> devote more transistors to accelerating code written in traditional languages, e.g., performing automatic prefetch, with hardware to detect linear access patterns on the fly. However the techniques may remain valid for throughput-oriented processors, which have a different throughput vs latency tradeoff, and may prefer to devote more area to execution units.
</p>
<h3>Scratchpad memory</h3>
<p>Some processors support <a href="/facts/Scratchpad_memory/qd5mHQul">scratchpad memory</a>  into which temporaries may be put, and <a href="/facts/Direct_memory_access/DWuVgclV">direct memory access</a> (DMA) to transfer data to and from <a href="/facts/Main_memory/wPHKFpdx">main memory</a> when needed. This approach is used by the <a href="/facts/Cell_(microprocessor)/p2MIQjMc">Cell processor</a>, and some <a href="/facts/Embedded_system/a4muX1wU">embedded systems</a>. These allow greater control over memory traffic and locality (as the working set is managed by explicit transfers), and eliminates the need for expensive <a href="/facts/Cache_coherency/MhUD576q">cache coherency</a> in a <a href="/facts/Manycore_processor/ozoxeNzT">manycore</a> machine.
</p><p>The disadvantage is it requires significantly different programming techniques to use. It is very hard to adapt programs written in traditional languages such as C and C++ which present the programmer with a uniform view of a large address space (which is an illusion simulated by caches). A traditional microprocessor can more easily run legacy code, which may then be accelerated by cache control instructions, whilst a scratchpad based machine requires dedicated coding from the ground up to even function. Cache control instructions are specific to a certain cache line size, which in practice may vary between generations of processors in the same architectural family. Caches may also help coalescing reads and writes from less predictable access patterns (e.g., during <a href="/facts/Texture_mapping/9gDTsuXN">texture mapping</a>), whilst scratchpad DMA requires reworking algorithms for more predictable 'linear' traversals.
</p><p>As such scratchpads are generally harder to use with traditional programming models, although <a href="/facts/Dataflow/jea04eH2">dataflow</a> models (such as <a href="/facts/TensorFlow/kDwfBeNd">TensorFlow</a>) might be more suitable.
</p>
<h3>Vector fetch</h3>
<p><a href="/facts/Vector_processor/nYAsIKT0">Vector processors</a> (for example modern <a href="/facts/Graphics_processing_unit/PTK1RQVp">graphics processing unit</a> (GPUs) and <a href="/facts/Xeon_Phi/Fv5dhyKc">Xeon Phi</a>) use massive <a href="/facts/Parallelism_(computing)/nQzcpzQt">parallelism</a> to achieve high throughput whilst working around memory latency (reducing the need for prefetching). Many read operations are issued in parallel, for subsequent invocations of a <a href="/facts/Compute_kernel/BxyI4vSf">compute kernel</a>; calculations may be put on hold awaiting future data, whilst the execution units are devoted to working on data from past requests data that has already turned up. This is easier for programmers to leverage in conjunction with the appropriate programming models (<a href="/facts/Compute_kernel/BxyI4vSf">compute kernels</a>), but harder to apply to general purpose programming.
</p><p>The disadvantage is that many copies of temporary states may be held in the <a href="/facts/Local_memory/Gg0UkuqW">local memory</a> of a <a href="/facts/Processing_element/Gg0UkuqW">processing element</a>, awaiting data in flight.
</p>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>"Power PC manual, see 1.10.3 Cache Control Instructions" (PDF). Archived from the original (PDF) on 2016-10-13. Retrieved 2016-06-11. <a href="https://web.archive.org/web/20161013060454/http://cache.nxp.com/files/32bit/doc/ref_manual/E500CORERM.pdf?fpsp=1&WT_TYPE=Reference%20Manuals&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation&fileExt=.pdf" target="_blank">https://web.archive.org/web/20161013060454/http://cache.nxp.com/files/32bit/doc/ref_manual/E500CORERM.pdf?fpsp=1&WT_TYPE=Reference%20Manuals&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation&fileExt=.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
</ol>

Cache control instruction open-in-new

Cache control instruction