All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 2/2] cpu: rearrange summary of chapter
Date: Sun, 14 Feb 2016 08:28:37 +0900	[thread overview]
Message-ID: <1455406117-6924-2-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1455406117-6924-1-git-send-email-sj38.park@gmail.com>

Summary of chapter and introduction about following chapters is in the
end part of `swdesign.tex` though it is not software design specific
content.  Moreover, the detailed introduction about following chapters
is in `cpu.tex`, too.  It would be better to gather them in one `tex`
file.  This commit gather them in `cpu.tex`.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 cpu/cpu.tex      | 13 +++++++++++++
 cpu/swdesign.tex | 13 -------------
 2 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/cpu/cpu.tex b/cpu/cpu.tex
index 6f1ae54..d765e71 100644
--- a/cpu/cpu.tex
+++ b/cpu/cpu.tex
@@ -43,6 +43,19 @@ text~\cite{Hennessy95a}.
 \input{cpu/hwfreelunch}
 \input{cpu/swdesign}

+So, to sum up:
+
+\begin{enumerate}
+\item	The good news is that multicore systems are inexpensive and
+	readily available.
+\item	More good news:  The overhead of many synchronization operations
+	is much lower than it was on parallel systems from the early 2000s.
+\item	The bad news is that the overhead of cache misses is still high,
+	especially on large systems.
+\end{enumerate}
+
+The remainder of this book describes ways of handling this bad news.
+
 In particular,
 Chapter~\ref{chp:Tools of the Trade} will cover some of the low-level
 tools used for parallel programming,
diff --git a/cpu/swdesign.tex b/cpu/swdesign.tex
index cdae106..4e9e91d 100644
--- a/cpu/swdesign.tex
+++ b/cpu/swdesign.tex
@@ -88,16 +88,3 @@ problem into one for which an embarrassingly parallel solution exists.
 	techniques to be used on the non-performance-critical bulk of
 	the program.
 } \QuickQuizEnd
-
-So, to sum up:
-
-\begin{enumerate}
-\item	The good news is that multicore systems are inexpensive and
-	readily available.
-\item	More good news:  The overhead of many synchronization operations
-	is much lower than it was on parallel systems from the early 2000s.
-\item	The bad news is that the overhead of cache misses is still high,
-	especially on large systems.
-\end{enumerate}
-
-The remainder of this book describes ways of handling this bad news.
-- 
1.9.1


  reply	other threads:[~2016-02-13 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-13 23:28 [PATCH 1/2] toolsoftrade: fix a typo SeongJae Park
2016-02-13 23:28 ` SeongJae Park [this message]
2016-02-15  6:12   ` [PATCH 2/2] cpu: rearrange summary of chapter Paul E. McKenney
2016-02-15  6:12 ` [PATCH 1/2] toolsoftrade: fix a typo Paul E. McKenney

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=1455406117-6924-2-git-send-email-sj38.park@gmail.com \
    --to=sj38.park@gmail.com \
    --cc=paulmck@linux.vnet.ibm.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.