From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Feedback on Chapter 9
Date: Thu, 21 Jul 2016 23:56:25 +0900 [thread overview]
Message-ID: <fedea970-dfd9-20cd-801c-009051debe4f@gmail.com> (raw)
Hi Paul,
I have a few comments on Chapter 9.
1st one is on the description of Figure 9.5.
When one reads the following,
> The ``ideal'' trace was generated by running the sequential code
> shown in Figure 9.2.
one might wonder, "Wait, why a sequential code scales with the number
of CPUs (threads)?"
Of course, route_lookup() of Figure 9.2 can be run concurrently on
multiple CPUs. But it might not be obvious for a novice reader.
Maybe you can make this as a Quick Quiz.
2nd one is for Figure 9.33.
Here, RCU QSBR (quiescent-state-based-reclamation) is mentioned.
However, there seems to be no explanation of what actually it is.
Do you plan to add some explanation or reference?
Thanks, Akira
next reply other threads:[~2016-07-21 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 14:56 Akira Yokosawa [this message]
2016-07-23 11:06 ` Feedback on Chapter 9 Akira Yokosawa
2016-07-25 0:36 ` 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=fedea970-dfd9-20cd-801c-009051debe4f@gmail.com \
--to=akiyks@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.