From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/4] count: Get rid of ACCESS_ONCE
Date: Wed, 3 Jan 2018 16:18:04 -0800 [thread overview]
Message-ID: <20180104001804.GA13670@linux.vnet.ibm.com> (raw)
In-Reply-To: <8134b352-67cd-2426-a3f7-ca776a3d7267@gmail.com>
On Sat, Dec 23, 2017 at 12:42:04PM +0900, Akira Yokosawa wrote:
> 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?
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
> 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(-)
>
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-01-04 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 3:42 [PATCH 0/4] count: Get rid of ACCESS_ONCE Akira Yokosawa
2017-12-23 3:43 ` [PATCH 1/4] count: Get rid of ACCESS_ONCE() in code snippet Akira Yokosawa
2017-12-23 3:44 ` [PATCH 2/4] count: Get rid of ACCESS_ONCE() in text Akira Yokosawa
2017-12-23 3:45 ` [PATCH 3/4] Update bibliography Akira Yokosawa
2017-12-23 3:46 ` [PATCH 4/4] toolsoftrade: Add quick quiz on ACCESS_ONCE() Akira Yokosawa
2018-01-04 0:18 ` Paul E. McKenney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180104001804.GA13670@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox