From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Yubin Ruan <ablacktshirt@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] defer: Correct grammar
Date: Sun, 29 Oct 2017 12:06:45 -0700 [thread overview]
Message-ID: <20171029190645.GJ3659@linux.vnet.ibm.com> (raw)
In-Reply-To: <3a7d438a-7b9c-8862-1f6e-3bc47e5f3c28@gmail.com>
On Sun, Oct 29, 2017 at 11:37:50AM +0800, Yubin Ruan wrote:
> >From 9d049c1dcc544588c12c989ff433fa88e999e4bb Mon Sep 17 00:00:00 2001
> From: Yubin Ruan <ablacktshirt@gmail.com>
> Date: Sun, 29 Oct 2017 11:36:21 +0800
> Subject: [PATCH] defer: Correct grammar
>
> Signed-off-by: Yubin Ruan <ablacktshirt@gmail.com>
Good catch, much clearer! Applied and pushed, thank you!
Thanx, Paul
> ---
> defer/rcufundamental.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
> index ef3e4d4..4c16478 100644
> --- a/defer/rcufundamental.tex
> +++ b/defer/rcufundamental.tex
> @@ -157,8 +157,8 @@ cause the values of \co{p->a}, \co{p->b}, and
> \co{p->c} to be fetched before the value of \co{p}.
> This is perhaps easiest to see in the case of value-speculation
> compiler optimizations, where the compiler guesses the value
> -of \co{p} fetches \co{p->a}, \co{p->b}, and
> -\co{p->c} then fetches the actual value of \co{p}
> +of \co{p}, fetches \co{p->a}, \co{p->b}, and
> +\co{p->c}, and then fetches the actual value of \co{p}
> in order to check whether its guess was correct.
> This sort of optimization is quite aggressive, perhaps insanely so,
> but does actually occur in the context of profile-driven optimization.
> --
> 2.7.4
>
prev parent reply other threads:[~2017-10-29 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 3:37 [PATCH] defer: Correct grammar Yubin Ruan
2017-10-29 19:06 ` 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=20171029190645.GJ3659@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ablacktshirt@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