whymb: Tweak width of Table C.1 for -eb builds
PATCH 1/2 whymb: Tweak width of Table C.1 for -eb builds
Commit ffdab3a2e986 ("whymb: Show "permissions" misses in C.1") made Table C.1 too wide for -eb builds.
Add \ebresizewidth{ ... } around the table.
Signed-off-by Akira Yokosawa <[email protected]>
--- appendix/whymb/whymemorybarriers.tex | 2 ++ 1 file changed, 2 insertions(+)
appendix/whymb/whymemorybarriers.tex +2 -0
@@ -562,6 +562,7 @@ are up to date (``V'') or not (``I''). \begin{table*} \small \centering +\ebresizewidth{ \renewcommand*{\arraystretch}{1.2} \rowcolors{6}{}{lightgray} \begin{tabular}{lclcccccc}
@@ -602,6 +603,7 @@ are up to date (``V'') or not (``I''). & $-$/I & 0/S & 0/S & $-$/I & I & V \\ \bottomrule \end{tabular} +} \caption{Cache Coherence Example} \label{tab:app:whymb:Cache Coherence Example} \end{table*}
base-commit: 61d5f16b87eeee8897af56f5e083b464919161f8
Signature · 1 line
2.34.1
PATCH 2/2 whymb: Fix staccato of "loads" and typos of "incuring"
Signed-off-by Akira Yokosawa <[email protected]>
--- appendix/whymb/whymemorybarriers.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
appendix/whymb/whymemorybarriers.tex +2 -2
@@ -611,7 +611,7 @@ are up to date (``V'') or not (``I''). Initially, the CPU cache lines in which the data would reside are in the ``invalid'' state, and the data is valid in memory, as shown in step~0. -In step~1, CPU~0 loads the data at address~0, incuring a cache miss, +In step~1, CPU~0 loads the data at address~0, incurring a cache miss, loading the value into its cache, and transitioning that cache line to the ``shared'' state. The contents of memory at address~0 remain valid.
@@ -664,7 +664,7 @@ However, because its cache holds that data in the ``modified'' state, CPU~2 can immediately execute that atomic increment without any change to cache or memory state. -In step~8.1, CPU~1 loads loads the data at address~0, incuring a cache +In step~8.1, CPU~1 loads the data at address~0, incurring a cache miss. Because the data from address~8 is modified in its cache, it must first flush that data to memory, transitioning its cache line to
Signature · 1 line
2.34.1
Quoted 6 lines · Akira Yokosawa
Commit
ffdab3a2e986("whymb: Show "permissions" misses in C.1") made Table C.1 too wide for -eb builds.Add \ebresizewidth{ ... } around the table.
Signed-off-by Akira Yokosawa <[email protected]>
Good eyes! Queued, thank you!
Thanx, Paul
Quoted 29 lines
--- appendix/whymb/whymemorybarriers.tex | 2 ++ 1 file changed, 2 insertions(+)appendix/whymb/whymemorybarriers.tex +2
-0@@ -562,6 +562,7 @@ are up to date (``V'') or not (``I''). \begin{table*} \small \centering +\ebresizewidth{ \renewcommand*{\arraystretch}{1.2} \rowcolors{6}{}{lightgray} \begin{tabular}{lclcccccc}@@ -602,6 +603,7 @@ are up to date (``V'') or not (``I''). & $-$/I & 0/S & 0/S & $-$/I & I & V \\ \bottomrule \end{tabular} +} \caption{Cache Coherence Example} \label{tab:app:whymb:Cache Coherence Example} \end{table*}base-commit:
61d5f16b87eeee8897af56f5e083b464919161f8Signature · 1 line
2.34.1