mirror of
https://github.com/cs341-illinois/coursebook.git
synced 2026-10-02 08:04:38 +08:00
Final fix for this issue
This commit is contained in:
@@ -55,7 +55,7 @@ This isn't a class about caching, know how this could impact your code.
|
||||
A short but non-complete list could be
|
||||
|
||||
\begin{enumerate}
|
||||
\item \hyperref[sec_race_conditions]{Race Conditions}! If a value is stored in two different processor caches, then that value should be accessed by a single thread.
|
||||
\item Race Conditions! If a value is stored in two different processor caches, then that value should be accessed by a single thread.
|
||||
\item Speed. With a cache, your program may look faster mysteriously. Just assume that reads and writes that either happened recently or are next to each other in memory are fast.
|
||||
\item Side effects. Every read or write effects the cache state. While most of the time this doesn't help or hurt, it is important to know. Check the Intel programmer guide on the lock prefix for more information.
|
||||
\end{enumerate}
|
||||
|
||||
Reference in New Issue
Block a user