From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 1/2] defer/hazptr: Fix a typo: updatesa -> updates
Date: Sat, 1 Jun 2019 06:37:21 -0700 [thread overview]
Message-ID: <20190601133721.GV28207@linux.ibm.com> (raw)
In-Reply-To: <20190601005425.22065-1-sj38.park@gmail.com>
On Sat, Jun 01, 2019 at 09:54:24AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good eyes, applied and pushed, thank you!
Thanx, Paul
> ---
> defer/hazptr.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/defer/hazptr.tex b/defer/hazptr.tex
> index b491c59..be93342 100644
> --- a/defer/hazptr.tex
> +++ b/defer/hazptr.tex
> @@ -332,7 +332,7 @@ object traversed.
> Therefore, hazard pointers's performance is far short of ideal.
> On the other hand, unlike naive approaches to concurrent reference-counting,
> hazard pointers do operate correctly for workloads
> -involving concurrent updatesa.
> +involving concurrent updates.
> Additional performance comparisons with other mechanisms may be found in
> Chapter~\ref{chp:Data Structures}
> and in other publications~\cite{ThomasEHart2007a,McKenney:2013:SDS:2483852.2483867,MagedMichael04a}.
> --
> 2.10.0
>
prev parent reply other threads:[~2019-06-01 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 0:54 [PATCH 1/2] defer/hazptr: Fix a typo: updatesa -> updates SeongJae Park
2019-06-01 0:54 ` [PATCH 2/2] together: Fix a wrong number of lines SeongJae Park
2019-06-01 13:37 ` 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=20190601133721.GV28207@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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.