From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/2] future: Update Locking and HTM comparison tables
Date: Wed, 6 Dec 2017 08:11:59 -0800 [thread overview]
Message-ID: <20171206161159.GX7829@linux.vnet.ibm.com> (raw)
In-Reply-To: <49209cfd-5494-fc54-ba4b-f8389ba4aed7@gmail.com>
On Thu, Dec 07, 2017 at 12:00:02AM +0900, Akira Yokosawa wrote:
> >From d6497dadbc973d7d94591f48730c4c0ce1c129a8 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 6 Dec 2017 23:40:04 +0900
> Subject: [PATCH 0/2] future: Update Locking and HTM comparison tables
>
> Hi Paul,
>
> I have tackled the remaining two tables of old style in Section 17.3.
> "Advantage", "Disadvantage", and "Strong Disadvantage" can be indicated
> by background colors, and their structures can be simplified.
> This scheme is inspired by Table 12.4, with using lower saturation
> colors.
>
> Patch #1 modifies the tables.
> Patch #2 adds a merged table of the two as a sidewaystable.
>
> Background colors are chosen so that they can be distinguished
> when they are printed in grayscale.
>
> Thoughts?
Very nice!!! I very much like the use of colors instead of symbols,
and I say that as someone who is red-green colorblind. ;-)
I queued both commits and added the commit below. If you are OK with
the below change, I will push all three. If not, please let me know
what needs to change.
Thanx, Paul
------------------------------------------------------------------------
commit 76dacd546e9e1ad1153ef5b3ef6ad0dfd9985246
Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Date: Wed Dec 6 08:07:10 2017 -0800
future/htm: Reword sentence referencing the new Table 17.3
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
diff --git a/future/htm.tex b/future/htm.tex
index 6667cd0ce8f0..908166bc0768 100644
--- a/future/htm.tex
+++ b/future/htm.tex
@@ -920,9 +920,11 @@ A summary of the differences between the two tables is as follows:
\input{future/HTMtableFull}
-For those who want to see the comparison at one view,
+For those with good eyesight,
Table~\ref{tab:future:Comparison of Locking (Plain and Augmented) and HTM}
-shows the merged comparison.
+combines
+Tables~\ref{tab:future:Comparison of Locking and HTM}
+and~\ref{tab:future:Comparison of Locking (Augmented by RCU or Hazard Pointers) and HTM}.
Of course, it is also possible to augment HTM,
as discussed in the next section.
next prev parent reply other threads:[~2017-12-06 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 15:00 [PATCH 0/2] future: Update Locking and HTM comparison tables Akira Yokosawa
2017-12-06 15:01 ` [PATCH 1/2] " Akira Yokosawa
2017-12-06 15:05 ` [PATCH 2/2] future: Add merged table of locking & HTM comparison Akira Yokosawa
2017-12-06 16:11 ` Paul E. McKenney [this message]
2017-12-06 22:16 ` [PATCH 0/2] future: Update Locking and HTM comparison tables Akira Yokosawa
2017-12-06 22:19 ` [PATCH v2 " Akira Yokosawa
2017-12-06 22:20 ` [PATCH v2 1/2] " Akira Yokosawa
2017-12-06 22:22 ` [PATCH v2 2/2] future: Add merged table of locking & HTM comparison Akira Yokosawa
2017-12-06 22:54 ` [PATCH v2 0/2] future: Update Locking and HTM comparison tables 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=20171206161159.GX7829@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