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] Some more hyphenation of compound words
Date: Sat, 13 Aug 2016 19:35:30 -0700	[thread overview]
Message-ID: <20160814023530.GF3482@linux.vnet.ibm.com> (raw)
In-Reply-To: <fde6fc31-0847-2395-0e7d-ecefcdb50444@gmail.com>

On Fri, Aug 12, 2016 at 06:12:32PM +0900, Akira Yokosawa wrote:
> >From 9761c723cb8a53b257878fd4fff0b042d0ccebbb Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 10 Aug 2016 20:30:56 +0900
> Subject: [PATCH] Some more hyphenation of compound words
> 
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>

Queued, thank you!

							Thanx, Paul

> ---
>  SMPdesign/criteria.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/SMPdesign/criteria.tex b/SMPdesign/criteria.tex
> index a84f301..f2f4602 100644
> --- a/SMPdesign/criteria.tex
> +++ b/SMPdesign/criteria.tex
> @@ -48,7 +48,7 @@ contention, overhead, read-to-write ratio, and complexity:
>  	This may be lock contention, memory contention, or a host
>  	of other performance killers.
>  \item[Work-to-Synchronization Ratio:]  A uniprocessor,
> -	single-threaded, non-preemptible, and non-interruptible\footnote{
> +	single\-/threaded, non-preemptible, and non\-/interruptible\footnote{
>  		Either by masking interrupts or by being oblivious to them.}
>  	version of a given parallel
>  	program would not need any synchronization primitives.
> -- 
> 1.9.1
> 


      reply	other threads:[~2016-08-14  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12  9:12 [PATCH] Some more hyphenation of compound words Akira Yokosawa
2016-08-14  2:35 ` 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=20160814023530.GF3482@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