All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junchang Wang <junchangwang@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, Junchang Wang <junchangwang@gmail.com>
Subject: [PATCH] SMPdesign: fix typos
Date: Fri, 16 Nov 2018 16:19:57 +0800	[thread overview]
Message-ID: <1542356397-14343-1-git-send-email-junchangwang@gmail.com> (raw)

Signed-off-by: Junchang Wang <junchangwang@gmail.com>
---
Hi list,

There are a few typos in Section Partitioning. Please take a look.

Thanks,
--Junchang

--
 SMPdesign/SMPdesign.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/SMPdesign/SMPdesign.tex b/SMPdesign/SMPdesign.tex
index 7b4f6eb..562c057 100644
--- a/SMPdesign/SMPdesign.tex
+++ b/SMPdesign/SMPdesign.tex
@@ -936,7 +936,7 @@ We could simply assign each CPU one gigabyte of memory, and allow
 each CPU to access its own private chunk of memory, without the
 need for locking and its complexities and overheads.
 Unfortunately, this simple scheme breaks down if an algorithm happens
-to have CPU~0 allocate all of the memory and CPU~1 the free it, as
+to have CPU~0 allocate all of the memory and CPU~1 free it, as
 would happen in a simple producer-consumer workload.

 The other extreme, code locking, suffers from excessive lock contention
@@ -1017,7 +1017,7 @@ smaller than the number of non-\co{NULL} pointers.
 The allocation function \co{memblock_alloc()} may be seen in
 Listing~\ref{lst:SMPdesign:Allocator-Cache Allocator Function}.
 Line~\lnref{pick} picks up the current thread's per-thread pool,
-and line~8 check to see if it is empty.
+and line~\lnref{chk:empty} checks to see if it is empty.

 If so, lines~\lnref{ack}-\lnref{rel} attempt to refill it
 from the global pool
-- 
2.7.4


             reply	other threads:[~2018-11-16  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16  8:19 Junchang Wang [this message]
2018-11-16 15:01 ` [PATCH] SMPdesign: fix typos Akira Yokosawa
2018-11-16 20:13   ` Paul E. McKenney
2018-11-17  8:26     ` Junchang Wang

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=1542356397-14343-1-git-send-email-junchangwang@gmail.com \
    --to=junchangwang@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.