From: zhouzhouyi@gmail.com
To: paulmck@kernel.org, akiyks@gmail.com, perfbook@vger.kernel.org
Cc: Zhouyi Zhou <zhouzhouyi@gmail.com>
Subject: [PATCH -perfbook v2] cpu: make Quick Quiz 3.6 more explicit
Date: Sat, 30 Dec 2023 08:07:24 +0800 [thread overview]
Message-ID: <1703894844-20798-1-git-send-email-zhouzhouyi@gmail.com> (raw)
From: Zhouyi Zhou <zhouzhouyi@gmail.com>
Rewrite Quick Quiz 3.6 for clarity and explicitness, so that the
firsttime reader know that another choice is CPU 0 sharing a core
with CPU 1.
This change was identified by Chinese version editor Yunjing Li in
the course of translating the book to Chinese.
Reported-by: Chinese version editor YunJing Li
Signed-off-by: Zhouyi Zhou<zhouzhouyi@gmail.com>
---
cpu/overheads.tex | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/cpu/overheads.tex b/cpu/overheads.tex
index 1ee9c52f..a2ec2998 100644
--- a/cpu/overheads.tex
+++ b/cpu/overheads.tex
@@ -262,7 +262,8 @@ CAS and lock, respectively.
\QuickQuiz{
\Cref{tab:cpu:CPU 0 View of Synchronization Mechanisms on 8-Socket System With Intel Xeon Platinum 8176 CPUs at 2.10GHz}
shows CPU~0 sharing a core with CPU~224.
- Shouldn't that instead be CPU~1???
+ However, isn't it more logical for CPU 0
+ to share a core with CPU 1 instead of CPU 224???
}\QuickQuizAnswer{
It is easy to be sympathetic to this view, but the file
\path{/sys/devices/system/cpu/cpu0/cache/index0/shared_cpu_list}
--
2.34.1
next reply other threads:[~2023-12-30 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 0:07 zhouzhouyi [this message]
2023-12-30 23:33 ` [PATCH -perfbook v2] cpu: make Quick Quiz 3.6 more explicit 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=1703894844-20798-1-git-send-email-zhouzhouyi@gmail.com \
--to=zhouzhouyi@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).