count: Get rid of ACCESS_ONCE
cover count: Get rid of ACCESS_ONCE
Hi Paul,
This patch set removes ACCESS_ONCE() in Chapter 5. (Yes, I saw the update in todo.txt.)
Patch #1 updates code snippets and code under CodeSamples/count/. Patch #2 updates text in Chapter 5 as well as Section 4.2.5 to adjust context. Citations in QQA to LWN article "ACCESS_ONCE()" is replaced by footnotes referencing definition in Section 4.2.5. Patch #3 adds a couple of git commits to bibliography to be cited by Patch #4.
Patch #4 adds a Quick Quiz in Section 4.2.5 to put a brief history of ACCESS_ONCE().
As ACCESS_ONCE() has been removed during Linux 4.15 merge window, it would be a good chance to put some memorial words in perfbook. In patch #4, I put them in a QQA. An alternative would be to
put them in a dedicated section on "compiler barriers" in Section 4.2 or 4.3.
In any case, the wording of the brief history needs some polishing by the inventor of ACCESS_ONCE(). So I don't expect patch #4 to be applied as is.
BTW, I thought twice about citing the git commit adding ACCESS_ONCE() in RCU code because of its title. Are you OK with it being listed in bibliography?
Thanks, Akira
--
Akira Yokosawa (4):
count: Get rid of ACCESS_ONCE() in code snippet
count: Get rid of ACCESS_ONCE() in text
Update bibliography
toolsoftrade: Add quick quiz on ACCESS_ONCE()
CodeSamples/count/count_lim_sig.c | 26 ++++++++++----------- CodeSamples/count/counttorture.h | 8 +++---- CodeSamples/count/limtorture.h | 18 +++++++------- bib/RCU.bib | 33 +++++++++++++++++++++++++- count/count.tex | 45 ++++++++++++++++++++--------------- toolsoftrade/toolsoftrade.tex | 49 ++++++++++++++++++++++++++++----------- 6 files changed, 119 insertions(+), 60 deletions(-)
Signature · 1 line
2.7.4
PATCH 1/4 count: Get rid of ACCESS_ONCE() in code snippet
PATCH 2/4 count: Get rid of ACCESS_ONCE() in text
In reply to Akira YokosawaPATCH 3/4 Update bibliography
In reply to Akira YokosawaPATCH 4/4 toolsoftrade: Add quick quiz on ACCESS_ONCE()
In reply to Akira YokosawaPaul E. McKenney
AppliedQuoted 19 lines · Akira Yokosawa
Hi Paul,
This patch set removes
ACCESS_ONCE()in Chapter 5. (Yes, I saw the update in todo.txt.)Patch #1 updates code snippets and code under CodeSamples/count/. Patch #2 updates text in Chapter 5 as well as Section 4.2.5 to adjust context. Citations in QQA to LWN article "
ACCESS_ONCE()" is replaced by footnotes referencing definition in Section 4.2.5. Patch #3 adds a couple of git commits to bibliography to be cited by Patch #4.
Patch #4 adds a Quick Quiz in Section 4.2.5 to put a brief history ofACCESS_ONCE().As
ACCESS_ONCE()has been removed during Linux 4.15 merge window, it would be a good chance to put some memorial words in perfbook. In patch #4, I put them in a QQA. An alternative would be to
put them in a dedicated section on "compiler barriers" in Section 4.2 or 4.3.
Quoted 7 lines
In any case, the wording of the brief history needs some polishing by the inventor of
ACCESS_ONCE(). So I don't expect patch #4 to be applied as is.BTW, I thought twice about citing the git commit adding
ACCESS_ONCE()in RCU code because of its title. Are you OK with it being listed in bibliography?
I queued these, thank you!
I reworked the answer to the new quick quiz. We might want to revisit the bibliography entries, but we are very likely going to have to cite git commits, so we might as well get started. ;-)
Thanx, Paul
Quoted 23 lines
Thanks, Akira
--
Akira Yokosawa (4):
count: Get rid ofACCESS_ONCE()in code snippet
count: Get rid ofACCESS_ONCE()in text
Update bibliography
toolsoftrade: Add quick quiz onACCESS_ONCE()CodeSamples/count/count_lim_sig.c | 26 ++++++++++----------- CodeSamples/count/counttorture.h | 8 +++---- CodeSamples/count/limtorture.h | 18 +++++++------- bib/RCU.bib | 33 +++++++++++++++++++++++++- count/count.tex | 45 ++++++++++++++++++++--------------- toolsoftrade/toolsoftrade.tex | 49 ++++++++++++++++++++++++++++----------- 6 files changed, 119 insertions(+), 60 deletions(-)Signature · 6 lines
2.7.4 -- To unsubscribe from this list: send the line "unsubscribe perfbook" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html