Write-once (cache coherence)

<h2 id="states">States</h2>
In this protocol, each block in the local cache is in one of these four states:

<ul><li>Invalid: This block has an incoherent copy of the memory.</li>
<li>Valid: This block has a coherent copy of the memory. The data may be possibly shared, but its content is not modified.</li>
<li>Reserved: The block is the only copy of the memory, but it is still coherent. No write-back is needed if the block is replaced.</li>
<li>Dirty: The block is the only copy of the memory and it is incoherent. This copy was written one or more times. This is the only state that generates a write-back when the block is replaced in the cache.</li></ul>
These states have exactly the same meanings as the four states of the <a href="/facts/MESI_protocol/BUCBWvtS">MESI protocol</a> (they are simply listed in reverse order), but this is a simplified form of it that avoids the Read for Ownership operation. Instead, all invalidation is done by writes to main memory.
For any given pair of caches, the permitted states of a given cache line are as follows (abbreviated in the order above):

<table><tbody><tr><th></th><th> I </th><th> V </th><th> R </th><th> D </th></tr><tr><th> I </th><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><th> V </th><td>Y</td><td>Y</td><td>N</td><td>N</td></tr><tr><th> R </th><td>Y</td><td>N</td><td>N</td><td>N</td></tr><tr><th> D </th><td>Y</td><td>N</td><td>N</td><td>N</td></tr></tbody></table>
<h2 id="transitions">Transitions</h2>
The protocol follows some transition rules for each event:

<ul><li>Read hit: The information is supplied by the current cache. No state change.</li>
<li>Read miss: The data is read from main memory. The read is <a href="/facts/Bus_sniffing/NUxKS0mb">snooped</a> by other caches; if any of them have the line in the Dirty state, the read is interrupted long enough to write the data back to memory before it is allowed to continue. Any copies in the Dirty or Reserved states are set to the Valid state.</li>
<li>Write hit: If the information in the cache is in Dirty or Reserved state, the cache line is updated in place and its state is set to Dirty without updating memory. If the information is in Valid state, a write-through operation is executed updating the block and the memory and the block state is changed to Reserved. Other caches snoop the write and set their copies to Invalid.</li>
<li>Write miss: A partial cache line write is handled as a read miss (if necessary to fetch the unwritten portion of the cache line) followed by a write hit. This leaves all other caches in the Invalid state, and the current cache in the Reserved state.</li></ul>
This is a variant of the MESI protocol, but there is no explicit read-for-ownership or broadcast invalidate operation to bring a line into cache in the Exclusive state without performing a main memory write. Instead, the first write to a Valid (a.k.a. Shared) cache line performs a write through to memory, which implicitly invalidates other caches. After that, the line is in the Reserved (Exclusive) state, and further writes can be done without reference to main memory, leaving the cache line in the Dirty (Modified) state.

<ul><li>Archibald, J.; Baer, J. L. (November 1986). "Cache coherence protocols: Evaluation using a multiprocessor simulation model". ACM Trans. Comput. Syst. 4 (4): 273–298. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1145%2F6513.6514">10.1145/6513.6514</a>. <a href="/facts/S2CID_(identifier)/ldJsHa2Y">S2CID</a> <a href="https://api.semanticscholar.org/CorpusID:713808">713808</a>.</li>
<li>Goodman, J. R. (1983). "Using cache memory to reduce processor-memory traffic". Proceedings of the 10th annual international symposium on Computer architecture - ISCA '83. International Symposium on Computer Architecture: Stockholm, Sweden, June 13–17, 1983. pp. 124–131. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1145%2F800046.801647">10.1145/800046.801647</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-89791-101-6.</li></ul>

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

<ol>
<li id="fn:1">Goodman, James R. (1983). "Using cache memory to reduce processor-memory traffic". ACM Sigarch Computer Architecture News. 11 (3): 124–131. doi:10.1145/1067651.801647. <a href="https://doi.org/10.1145%2F1067651.801647" target="_blank">https://doi.org/10.1145%2F1067651.801647</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
</ol>

Write-once (cache coherence) open-in-new

Write-once (cache coherence)