From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Junchang Wang <junchangwang@gmail.com>, perfbook@vger.kernel.org
Subject: Re: [PATCH] count: Fix typo in Answer to Quick Quiz 5.27
Date: Wed, 10 May 2017 20:15:43 -0700 [thread overview]
Message-ID: <20170511031543.GC3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <c324d63f-7da2-2c9c-f99f-c74fecb2bcc3@gmail.com>
On Thu, May 11, 2017 at 09:47:58AM +0900, Akira Yokosawa wrote:
> >From 557aa593d97bf2b8cc47ff14fbcaf3f80703866a Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Tue, 9 May 2017 23:39:57 +0900
> Subject: [PATCH] count: Fix typo in Answer to Quick Quiz 5.27
>
> Reported-by: Junchang Wang <junchangwang@gmail.com>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> Acked-by: Junchang Wang <junchangwang@gmail.com>
Queued and pushed, thank you both!
Thanx, Paul
> ---
> count/count.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/count/count.tex b/count/count.tex
> index cc47554..096b53d 100644
> --- a/count/count.tex
> +++ b/count/count.tex
> @@ -1260,7 +1260,7 @@ machine.
> \QuickQuizAnswer{
> One approach would be to maintain a global approximation
> to the value.
> - Readers would increment their per-thread variable, but when it
> + Updaters would increment their per-thread variable, but when it
> reached some predefined limit, atomically add it to a global
> variable, then zero their per-thread variable.
> This would permit a tradeoff between average increment overhead
> --
> 2.7.4
>
>
prev parent reply other threads:[~2017-05-11 3:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 8:48 [PATCH] Update Answer to Quick Quiz 5.27 Junchang Wang
2017-05-09 14:56 ` Akira Yokosawa
2017-05-09 15:21 ` Junchang Wang
2017-05-09 22:38 ` Akira Yokosawa
2017-05-09 23:05 ` Junchang Wang
2017-05-11 0:47 ` [PATCH] count: Fix typo in " Akira Yokosawa
2017-05-11 3:15 ` 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=20170511031543.GC3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=junchangwang@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.