All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/6] count: Employ new code-snippet scheme (cont.)
Date: Sun, 14 Oct 2018 17:16:39 -0700	[thread overview]
Message-ID: <20181015001639.GO2674@linux.ibm.com> (raw)
In-Reply-To: <a20c67f0-db94-7e03-ed69-d09fd51899dd@gmail.com>

On Sat, Oct 13, 2018 at 11:52:50PM +0900, Akira Yokosawa wrote:
> Hi Paul,
> 
> count_lim_sig.c was a hard one to review for me regarding the usage
> of READ_ONCE()/WRITE_ONCE(). Patch #5 is my attempt to add several
> of them. There might be other combination of racy accesses.
> 
> Patches #1--#4 are trivial ones.
> 
> Patch #6 is the result of quick review of your recent addition to
> toolsoftrade.  I'm not sure you like the addition of comments
> "/* BUGGY!!! */" to Lisitngs which look irrelevant to their
> captions.
> 
> Patches #5 and #6 are more likely to need your close look.

It looks good from what I can see, though your patch 6/6 should
limit your confidence in this.  ;-)

I folded your later 7/6 into 4/6.

Queued and pushed, thank you!!!

							Thanx, Paul

>         Thanks, Akira
> --
> Akira Yokosawa (6):
>   count: Employ new scheme for snippet of count_lim_app
>   count: Fix uses of READ/WRITE_ONCE() in count_lim_app
>   count: Employ new scheme for snippet of count_lim_atomic
>   count: Employ new scheme for snippet of count_lim_sig
>   count: READ/WRITE_ONCE() tweaks for count_lim_sig
>   toolsoftrade: Proofread newly added sections
> 
>  CodeSamples/count/count_lim_app.c    |  17 +-
>  CodeSamples/count/count_lim_atomic.c | 209 ++++----
>  CodeSamples/count/count_lim_sig.c    | 159 ++++---
>  count/count.tex                      | 892 ++++++++++-------------------------
>  toolsoftrade/toolsoftrade.tex        |  44 +-
>  5 files changed, 494 insertions(+), 827 deletions(-)
> 
> -- 
> 2.7.4
> 


      parent reply	other threads:[~2018-10-15  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13 14:52 [PATCH 0/6] count: Employ new code-snippet scheme (cont.) Akira Yokosawa
2018-10-13 14:53 ` [PATCH 1/6] count: Employ new scheme for snippet of count_lim_app Akira Yokosawa
2018-10-13 14:54 ` [PATCH 2/6] count: Fix uses of READ/WRITE_ONCE() in count_lim_app Akira Yokosawa
2018-10-13 14:56 ` [PATCH 3/6] count: Employ new scheme for snippet of count_lim_atomic Akira Yokosawa
2018-10-13 14:56 ` [PATCH 4/6] count: Employ new scheme for snippet of count_lim_sig Akira Yokosawa
2018-10-13 14:58 ` [PATCH 5/6] count: READ/WRITE_ONCE() tweaks for count_lim_sig Akira Yokosawa
2018-10-13 14:59 ` [PATCH 6/6] toolsoftrade: Proofread newly added sections Akira Yokosawa
2018-10-13 23:15 ` [PATCH 7/6] count: Fix typo (missing \lnref) Akira Yokosawa
2018-10-15  0:16 ` 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=20181015001639.GO2674@linux.ibm.com \
    --to=paulmck@linux.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 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.