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: [RFC PATCH 07/12] advsync: Substitute 'guarantee' with 'implication'
Date: Sat, 1 Apr 2017 11:17:24 +0900	[thread overview]
Message-ID: <c3bdc26e-332a-a7fd-2681-050d691f93d8@gmail.com> (raw)
In-Reply-To: <b00db59a-a0b0-42d6-7546-01872ad3e404@gmail.com>

From 8dac6729398f02c38bbe9df6b4ad137678420ac6 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Sun, 26 Mar 2017 09:36:22 +0900
Subject: [RFC PATCH 07/12] advsync: Substitute 'guarantee' with 'implication'

Modify wording to go along with what is found in current
memory-barriers.txt. (Although this part is under Section
"LOCK ACQUISITION FUNCTIONS" now.)

Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
 advsync/memorybarriers.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
index 6215311..64d78f4 100644
--- a/advsync/memorybarriers.tex
+++ b/advsync/memorybarriers.tex
@@ -2727,35 +2727,35 @@ barriers throughout.
 \label{sec:advsync:Locking Constraints}

 As noted earlier, locking primitives contain implicit memory barriers.
-These implicit memory barriers provide the following guarantees:
+These primitives imply the following:
 \begin{enumerate}
-\item	ACQUIRE operation guarantee:
+\item	ACQUIRE operation implication:
 	\begin{itemize}
 	\item	Memory operations issued after an ACQUIRE will be completed
 		after the ACQUIRE operation has completed.
 	\item	Memory operations issued before an ACQUIRE may be completed
 		after the ACQUIRE operation has completed.
 	\end{itemize}
-\item	RELEASE operation guarantee:
+\item	RELEASE operation implication:
 	\begin{itemize}
 	\item	Memory operations issued before a RELEASE will be
 		completed before the RELEASE operation has completed.
 	\item	Memory operations issued after a RELEASE may be completed
 		before the RELEASE operation has completed.
 	\end{itemize}
-\item	ACQUIRE vs ACQUIRE guarantee:
+\item	ACQUIRE vs ACQUIRE implication:
 	\begin{itemize}
 	\item	All ACQUIRE operations issued before another ACQUIRE operation
 		will be completed before that ACQUIRE operation.
 	\end{itemize}
-\item	ACQUIRE vs RELEASE guarantee:
+\item	ACQUIRE vs RELEASE implication:
 	\begin{itemize}
 	\item	All ACQUIRE operations issued before a RELEASE operation
 		will be completed before the RELEASE operation.
 	\item	All RELEASE operations issued before an ACQUIRE operation
 		will be completed before the ACQUIRE operation.
 	\end{itemize}
-\item	Failed conditional ACQUIRE guarantee:
+\item	Failed conditional ACQUIRE implication:
 	\begin{itemize}
 	\item	Certain variants of ACQUIRE operation may fail, either
 		due to being unable to get the lock immediately, or due
-- 
2.7.4



  parent reply	other threads:[~2017-04-01  2:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01  2:09 [RFC PATCH 00/12] advsync: Rename LOCK/UNLOCK to ACQUIRE/RELEASE Akira Yokosawa
2017-04-01  2:10 ` [RFC PATCH 01/12] advsync: LOCK/UNLOCK -> ACQUIRE/RELEASE (part 1) Akira Yokosawa
2017-04-01  2:11 ` [RFC PATCH 02/12] advsync: LOCK/UNLOCK -> ACQUIRE/RELEASE (part 2) Akira Yokosawa
2017-04-01  2:12 ` [RFC PATCH 03/12] advsync: LOCK/UNLOCK -> ACQUIRE/RELEASE (part 3) Akira Yokosawa
2017-04-01  2:13 ` [RFC PATCH 04/12] advsync: More replacement to ACQUIRE Akira Yokosawa
2017-04-01  2:14 ` [RFC PATCH 05/12] advsync: Add footnote mentioning LOCK/UNLOCK wording Akira Yokosawa
2017-04-01  2:16 ` [RFC PATCH 06/12] advsync: Modify usage of definite article Akira Yokosawa
2017-04-01  2:17 ` Akira Yokosawa [this message]
2017-04-01  2:19 ` [RFC PATCH 08/12] advsync: Properly use nbsp Akira Yokosawa
2017-04-01  2:21 ` [RFC PATCH 09/12] advsync: Move footnote on transitivity forward Akira Yokosawa
2017-04-01  2:22 ` [RFC PATCH 10/12] advsync: Fix line number called out Akira Yokosawa
2017-04-01  2:23 ` [RFC PATCH 11/12] advsync: Add extdash shortcut Akira Yokosawa
2017-04-01  2:23 ` [RFC PATCH 12/12] advsync: Avoid indent after minipage Akira Yokosawa
2017-04-04 16:02 ` [RFC PATCH 00/12] advsync: Rename LOCK/UNLOCK to ACQUIRE/RELEASE 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=c3bdc26e-332a-a7fd-2681-050d691f93d8@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.