All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH 00/14] advsync: Use pseudo asm in code sequence
Date: Mon, 17 Apr 2017 07:11:37 +0900	[thread overview]
Message-ID: <be8c3cb5-9ee2-9f60-bfcd-e729389304f9@gmail.com> (raw)

From 6efc224d8e6d2b64bf7a86b52d03de01ccea7032 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Mon, 17 Apr 2017 06:53:11 +0900
Subject: [PATCH 00/14] advsync: Use pseudo asm in code sequence

Hi Paul,

This series substitutes pseudo-asm codes for C style statements
in code sequences in 'Memory Barrier' section.

Other than the substitution, Patch 2 replaces ACCESS_ONCE(),
Patch 4 is a backport of the changes made in memory-barriers.txt,
Patches 8 and 12 add footnotes to imply the necessity of data
dependency barrier, and Patch 11 renames Section "Guarantee"
to "Minimal Guarantee".

My guess is that the original intention of the "Guarantee"
section was to present minimal guarantees free of memory barriers.
When the necessity of read dependency barrier was recognized,
the barrier sneaked into this section.

In LaTeX, as footnotes can prevent readers' misunderstanding,
We can preserve the original intention.

Thoughts?

                                  Thanks Akira
--
Akira Yokosawa (14):
  advsync: Use pseudo asm in sequence in 'Paring' section
  advsync: Substitute READ_ONCE()/WRITE_ONCE() for ACCESS_ONCE()
  advsync: Use pseudo asm in sequence in 'Review of Locking Impl'
  advsync: Backport upstream commits regarding reordering example
  advsync: Use pseudo asm in reordering example
  advsync: Use pseudo asm in another reordering example
  advsync: Avoid indent after minipages
  advsync: Add footnote to imply necessity of data dependency barrier
  advsync: Use READ_ONCE()/WRITE_ONCE() in sequence of 'Device
    Operations'
  advsync: Use READ_ONCE()/WRITE_ONCE() in sequence in 'Guarantees'
  advsync: Rename Section 'Guarantee' to 'Minimal Guarantee'
  advsync: Add another footnote implying data dependency barrier
  advsync: Use pseudo asm in sequence in 'Data Dependency Barriers'
  advsync: Use pseudo asm in sequence in 'SMP Barrier Pairing'

 advsync/memorybarriers.tex | 321 ++++++++++++++++++++++++---------------------
 1 file changed, 172 insertions(+), 149 deletions(-)

-- 
2.7.4


             reply	other threads:[~2017-04-16 22:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 22:11 Akira Yokosawa [this message]
2017-04-16 22:13 ` [PATCH 01/14] advsync: Use pseudo asm in sequence in 'Paring' section Akira Yokosawa
2017-04-16 22:14 ` [PATCH 02/14] advsync: Substitute READ_ONCE()/WRITE_ONCE() for ACCESS_ONCE() Akira Yokosawa
2017-04-16 22:15 ` [PATCH 03/14] advsync: Use pseudo asm in sequence in 'Review of Locking Impl' Akira Yokosawa
2017-04-16 22:17 ` [PATCH 04/14] advsync: Backport upstream commits regarding reordering example Akira Yokosawa
2017-04-16 22:18 ` [PATCH 05/14] advsync: Use pseudo asm in " Akira Yokosawa
2017-04-16 22:19 ` [PATCH 06/14] advsync: Use pseudo asm in another " Akira Yokosawa
2017-04-16 22:19 ` [PATCH 07/14] advsync: Avoid indent after minipages Akira Yokosawa
2017-04-16 22:20 ` [PATCH 08/14] advsync: Add footnote to imply necessity of data dependency barrier Akira Yokosawa
2017-04-16 22:22 ` [PATCH 09/14] advsync: Use READ_ONCE()/WRITE_ONCE() in sequence of 'Device Operations' Akira Yokosawa
2017-04-16 22:23 ` [PATCH 10/14] advsync: Use READ_ONCE()/WRITE_ONCE() in sequence in 'Guarantees' Akira Yokosawa
2017-04-16 22:24 ` [PATCH 11/14] advsync: Rename Section 'Guarantees' to 'Minimal Guarantees' Akira Yokosawa
2017-04-16 22:25 ` [PATCH 12/14] advsync: Add another footnote implying data dependency barrier Akira Yokosawa
2017-04-16 22:26 ` [PATCH 13/14] advsync: Use pseudo asm in sequence in 'Data Dependency Barriers' Akira Yokosawa
2017-04-16 22:27 ` [PATCH 14/14] advsync: Use pseudo asm in sequence in 'SMP Barrier Pairing' Akira Yokosawa
2017-04-17 15:39 ` [PATCH 00/14] advsync: Use pseudo asm in code sequence Paul E. McKenney

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=be8c3cb5-9ee2-9f60-bfcd-e729389304f9@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.