Discussions of the Parallel Programming book
 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/4] Misc updates
Date: Tue, 4 Dec 2018 08:40:00 -0800	[thread overview]
Message-ID: <20181204164000.GY4170@linux.ibm.com> (raw)
In-Reply-To: <b5e1d894-aed2-0171-7cbc-12a46d67bfb6@gmail.com>

On Wed, Dec 05, 2018 at 12:27:34AM +0900, Akira Yokosawa wrote:
> >From 5471262067bf42e8698c80fee3e1d42a8c576d43 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 5 Dec 2018 00:10:12 +0900
> Subject: [PATCH 0/4] Misc updates
> 
> Hi Paul,
> 
> As I reported this September, Figure 5.1 is not complete yet.
> As a workaround, patches #1 and #2 restores the old plot of
> Nehalem for Figure 5.1.  Once we can obtain complete data,
> it should be easy to update again.
> 
> Patch #3 is a minor tweak in RCU code snippets to prevent
> short code snippets from being page/column broken.
> 
> Patch #4 fixes a typo in an epigraph you've added recently.
> 
> Hopefully, this would be a final patch set from me for the
> upcoming release.

Applied and pushed, thank you!  And good point, and same for me -- no
more commits authored by me (except for minor fixes) until the release.
Of course, I also welcome minor fixes from others.  Large changes are
also still welcome, but I will instead add them to a branch to be merged
afterthe release.

							Thanx, Paul

>         Thanks, Akira
> --
> Akira Yokosawa (4):
>   CodeSamples/count: Restore atomic125.eps
>   count: Restore 'fig:count:Atomic Increment Scalability on Nehalem'
>   defer: Prevent page/column break in short inline code snippets
>   owned: Fix typo in epigraph
> 
>  CodeSamples/count/atomic125.eps      |  856 +++++++------
>  CodeSamples/count/atomic125.png      |  Bin 3189 -> 3337 bytes
>  CodeSamples/count/atomic_nehalem.eps | 2266 ++++++++++++++++++++++++++++++++++
>  count/count.tex                      |   14 +-
>  defer/rcufundamental.tex             |   14 +-
>  defer/rcuintro.tex                   |    4 +-
>  locking/locking.tex                  |    2 +-
>  owned/owned.tex                      |    2 +-
>  8 files changed, 2770 insertions(+), 388 deletions(-)
>  create mode 100644 CodeSamples/count/atomic_nehalem.eps
> 
> -- 
> 2.7.4
> 


      parent reply	other threads:[~2018-12-04 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 15:27 [PATCH 0/4] Misc updates Akira Yokosawa
2018-12-04 15:28 ` [PATCH 1/4] CodeSamples/count: Restore atomic125.eps Akira Yokosawa
2018-12-04 15:30 ` [PATCH 2/4] count: Restore 'fig:count:Atomic Increment Scalability on Nehalem' Akira Yokosawa
2018-12-04 15:31 ` [PATCH 3/4] defer: Prevent page/column break in short inline code snippets Akira Yokosawa
2018-12-04 15:32 ` [PATCH 4/4] owned: Fix typo in epigraph Akira Yokosawa
2018-12-04 16:40 ` 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=20181204164000.GY4170@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox