Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/6] advsync: Misc. fixes around litmus tests
Date: Thu, 13 Jul 2017 11:12:24 -0700	[thread overview]
Message-ID: <20170713181224.GA16934@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170713180343.GN2393@linux.vnet.ibm.com>

On Thu, Jul 13, 2017 at 11:03:43AM -0700, Paul E. McKenney wrote:
> On Thu, Jul 13, 2017 at 12:07:18AM +0900, Akira Yokosawa wrote:
> > >From de45acd5a73354cbe03abaf3130177687c77e4cb Mon Sep 17 00:00:00 2001
> > From: Akira Yokosawa <akiyks@gmail.com>
> > Date: Wed, 12 Jul 2017 23:45:17 +0900
> > Subject: [PATCH 0/6] advsync: Misc. fixes around litmus tests
> > 
> > Hi Paul,
> > 
> > This patch set tries to cleanup recently updated material in advsync.
> > 
> > Patches 1 to 3 are fixes of litmus tests under CodeSamples/advsync/herd
> > and their corresponding snippets in memorybarriers.tex.
> > 
> > Patch 4 is trivial fixes.
> > 
> > Patch 5 is my attempt for the sentence to make sense.
> > 
> > Patch 6 updates the usage of x0 and x1 in the tables of Store-Buffering
> > Sequence of Events. I stopped short of using READ_ONCE() and WRITE_ONCE()
> > in the "Instruction" columns. The change seems unnecessary for me.
> > I think we can assume a reader of this section can easily translate
> > READ_ONCE() and WRITE_ONCE() to simple assignments in his/her mind.
> > Also, you are calling x0 and x1 as if they are variables in the text.
> > But I don't think the current way of description is ambiguous.
> > 
> > So, Patches 1 to 4 should be all right. You might feel otherwise to
> > Patches 5 and 6.
> 
> Good catches, thank you!!!
> 
> The only think I didn't take was the addition of indirection to the
> variables in the tables.  The litmus tests have the indirection on
> the function parameters, and omit it in the exists clause.  So there
> is potential for confusion either way.  So I came down on the side of
> the shortest way, that is, omitting the indirection.
> 
> And yes, my original tables were inconsistent!  ;-)
> 
> I also took your 7/6 patch, and thank you again.

And kernel.org is having some issues, so I pushed to my github
perfbook repo.  Hopefully kernel.org will be feeling better later...

							Thanx, Paul

> > Thoughts?
> > 
> >             Thanks, Akira
> > -- 
> > Akira Yokosawa (6):
> >   advsync: Fix typo of litmus name
> >   advsync: Fix typos in load-buffering litmus tests
> >   advsync: Fix remaining typo in exists condition
> >   advsync: Trivial typo fixes
> >   advsync: Fix grammatical error
> >   advsync: Adjust value expressions in Tables 14.1 and 14.2
> > 
> >  CodeSamples/advsync/herd/C-LB+o-o+o-o.litmus       |   2 +-
> >  CodeSamples/advsync/herd/C-LB+o-r+a-o.litmus       |   4 +-
> >  .../advsync/herd/C-MP+o-wmb-o+o-rmb-o.litmus       |   2 +-
> >  advsync/memorybarriers.tex                         | 103 ++++++++++-----------
> >  4 files changed, 55 insertions(+), 56 deletions(-)
> > 
> > -- 
> > 2.7.4
> > 


      reply	other threads:[~2017-07-13 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 15:07 [PATCH 0/6] advsync: Misc. fixes around litmus tests Akira Yokosawa
2017-07-12 15:08 ` [PATCH 1/6] advsync: Fix typo of litmus name Akira Yokosawa
2017-07-12 15:10 ` [PATCH 2/6] advsync: Fix typos in load-buffering litmus tests Akira Yokosawa
2017-07-12 15:10 ` [PATCH 3/6] advsync: Fix remaining typo in exists condition Akira Yokosawa
2017-07-12 15:11 ` [PATCH 4/6] advsync: Trivial typo fixes Akira Yokosawa
2017-07-12 15:13 ` [PATCH 5/6] advsync: Fix grammatical error Akira Yokosawa
2017-07-12 15:14 ` [PATCH 6/6] advsync: Adjust value expressions in Tables 14.1 and 14.2 Akira Yokosawa
2017-07-13 13:38 ` [PATCH 7/6] advsync: Catch up changes in litmus tests Akira Yokosawa
2017-07-13 18:03 ` [PATCH 0/6] advsync: Misc. fixes around " Paul E. McKenney
2017-07-13 18:12   ` 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=20170713181224.GA16934@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