Invalidating cache line
If a thread reads data not present in any cache, it will fetch the line into its cache in exclusive state (E): If a thread reads from a cache line that is in exclusive state (E) in another thread's cache, it fetches the cache line to its cache in shared state (S) and downgrades the cache line to shared state (S) in the other cache: If a thread reads from a cache line that is in modified state (M) in another thread's cache, the other cache must first write-back its modified version of the cache line and downgrade it to shared state (S).
Important You can invalidate most types of objects that are served by a web distribution, but you cannot invalidate media files in the Microsoft Smooth Streaming format when you have enabled Smooth Streaming for the corresponding cache behavior.
If you submit more than the allotted number of invalidation paths in a month, you pay a fee for each invalidation path that you submit.
For more information about the charges for invalidation, see Paying for Object Invalidation.
If we translate before we go to the cache, we have a "". We must flush the cache on a context switch to avoid "aliasing".In addition, you cannot invalidate objects that are served by an RTMP distribution.You can submit a specified number of invalidation paths each month for free.A cache with a write-through policy (and write-allocate) read an entire block (cacheline) from memory on a cache miss and writes only the updated item to memory for a store. A cache with a write-back policy (and write-allocate) reads an entire block (cacheline) from memory on a cache miss, may need to write dirty cacheline first.Any writes to memory need to be the entire cacheline since no way to distinguish which word was dirty with only a single dirty bit.