diff options
| author | SeongJae Park <sj38.park@gmail.com> | 2023-09-23 09:32:03 -0700 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2023-09-24 07:44:25 -0700 |
| commit | b4f44b7a4973df819fabdc5cf5050b11617b2559 (patch) | |
| tree | 2e61f463ba570d41d715cdf9b8c60032ce78f169 | |
| parent | 4e32aa641b3487085de6df4d87e2b48658442da2 (diff) | |
| download | perfbook-b4f44b7a4973df819fabdc5cf5050b11617b2559.tar.gz | |
memorder: Make clear the scope of READ_ONCE()/WRITE_ONCE() heavy uses
A sentence in memorder.tex is saying READ_ONCE() and WRITE_ONCE() will
be heavily used in a section. But, it's widely used in the chapter.
Modify the sentence to make it more clear.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
| -rw-r--r-- | memorder/memorder.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/memorder/memorder.tex b/memorder/memorder.tex index bd24b14c..5c978fbe 100644 --- a/memorder/memorder.tex +++ b/memorder/memorder.tex @@ -668,7 +668,7 @@ even on relatively strongly ordered systems such as x86. \co{READ_ONCE()} and \co{WRITE_ONCE()} prevent the compiler from reordering. And also from doing much else as well, so the examples in this - section will be making heavy use of + chapter will be making heavy use of \co{READ_ONCE()} and \co{WRITE_ONCE()}. See \cref{sec:memorder:Compile-Time Consternation} for more detail on the need for \co{READ_ONCE()} and \co{WRITE_ONCE()}. |