From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] intro: Polish a sentence for MIPS graphs
Date: Sun, 11 Mar 2018 19:10:01 -0700 [thread overview]
Message-ID: <20180312021001.GP3918@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180311125241.30343-1-sj38.park@gmail.com>
On Sun, Mar 11, 2018 at 09:52:41PM +0900, SeongJae Park wrote:
> This commit polishes a sentence for MIPS graphs, which is updated by
> commit "cpu: Update MIPS graphs, adding past five years of CPUs"
> (71d8328f3d18). The sentence is saying that the updated graph is
> showing past three decades, though it is now showing past forty years
> and the sentence also says so at last. This commit polishes the
> sentence to say about the fourty years.
>
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good catch, applied, thank you!
Thanx, Paul
> ---
> intro/intro.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/intro/intro.tex b/intro/intro.tex
> index a4ec3a8..2f5679d 100644
> --- a/intro/intro.tex
> +++ b/intro/intro.tex
> @@ -449,7 +449,7 @@ The CSIRAC and the Z80 are two points in a long-term trend, as can be
> seen in
> Figure~\ref{fig:intro:MIPS per Die for Intel CPUs}.
> This figure plots an approximation to computational power per die
> -over the past three decades, showing an impressive six-order-of-magnitude
> +over the past four decades, showing an impressive six-order-of-magnitude
> increase over a period of forty years.
> Note that the advent of multicore CPUs has permitted this increase to
> continue apace despite the clock-frequency wall encountered in 2003,
> --
> 2.10.0
>
prev parent reply other threads:[~2018-03-12 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 12:52 [PATCH] intro: Polish a sentence for MIPS graphs SeongJae Park
2018-03-12 2:10 ` 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=20180312021001.GP3918@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.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.