Write-back vs Write-Through caching?

by

The benefit of write-through to main memory is that it simplifies the design of the computer system. With write-through, the main memory always has an up-to-date copy of the line. So when a read is done, main memory can always reply with the requested data.

If write-back is used, sometimes the up-to-date data is in a processor cache, and sometimes it is in main memory. If the data is in a processor cache, then that processor must stop main memory from replying to the read request, because the main memory might have a stale copy of the data. This is more complicated than write-through.

Also, write-through can simplify the cache coherency protocol because it doesn’t need the Modify state. The Modify state records that the cache must write back the cache line before it invalidates or evicts the line. In write-through a cache line can always be invalidated without writing back since memory already has an up-to-date copy of the line.

One more thing – on a write-back architecture software that writes to memory-mapped I/O registers must take extra steps to make sure that writes are immediately sent out of the cache. Otherwise writes are not visible outside the core until the line is read by another processor or the line is evicted.

More Related Contents:

  1. Why is the size of L1 cache smaller than that of the L2 cache in most of the processors?
  2. Line size of L1 and L2 caches
  3. VIPT Cache: Connection between TLB & Cache?
  4. How does one write code that best utilizes the CPU cache to improve performance?
  5. Virtually indexed physically tagged cache Synonym
  6. What Every Programmer Should Know About Memory?
  7. What is a “cache-friendly” code?
  8. Memcached vs. Redis? [closed]
  9. How much of ‘What Every Programmer Should Know About Memory’ is still valid?
  10. Better Way to Prevent IE Cache in AngularJS?
  11. Chrome doesn’t cache images/js/css
  12. Do current x86 architectures support non-temporal loads (from “normal” memory)?
  13. Where is the Write-Combining Buffer located? x86
  14. Redis: possible to expire an element in an array or sorted set?
  15. What does it mean by cold cache and warm cache concept?
  16. How to force browsers to reload cached CSS and JS files?
  17. Tomcat 8 throwing – org.apache.catalina.webresources.Cache.getResource Unable to add the resource
  18. Difference between no-cache and must-revalidate for Cache-Control?
  19. What does a ‘Split’ cache means. And how is it useful(if it is)?
  20. Cycles/cost for L1 Cache hit vs. Register on x86?
  21. What’s default value of cache-control?
  22. System.Web.Caching vs. Enterprise Library Caching Block
  23. How does Linux perf calculate the cache-references and cache-misses events
  24. WP7 HttpWebRequest without caching
  25. How do the store buffer and Line Fill Buffer interact with each other?
  26. How to clear CPU L1 and L2 cache [duplicate]
  27. How to prevent Browser cache on Angular 2 site?
  28. RAM drive for compiling – is there such a thing?
  29. What specifically marks an x86 cache line as dirty – any write, or is an explicit change required?
  30. When does browser automatically clear cache of external JavaScript file?

Leave a Comment