A policy that, on a write miss, first brings the line into the cache and then writes it. Usually paired with write-back; writing directly to the lower level without fetching is called no-write-allocate.
Field: Memory Hierarchy
Whether to load a line on a write miss is the write-allocate decision, separate from the write buffer.
What is the main purpose of a write buffer in a write-throu…Writing straight to the lower level on a write miss without loading the line is no-write-allocate, commonly paired with write-through.
Which policy, on a write miss, writes directly to the lower…Ordinary stores with write-allocate fetch the line from memory before writing, so even write-only data costs read traffic and evicts other data that will be reused.
When writing out a large amount of data that will not be re…Write-through Miss penalty Average memory access time Cache line Capacity miss Compulsory miss Conflict miss Direct-mapped cache Fully associative cache Loop blocking