From: "Leonardo Brás" <leobras.c@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org
Subject: Question about Table E.1
Date: Wed, 08 Feb 2023 00:07:20 -0300 [thread overview]
Message-ID: <fba1fe891b65449475c1e4e9abee2d3337c1567c.camel@gmail.com> (raw)
Hello Paul,
I have been reading the book, until I stumbled on Quick Quiz 3.7,
Table E.1: Performance of Synchronization Mechanisms
on 16-CPU 2.8 GHz Intel X5550 (Nehalem) System
<Copying from source, since the PDF is a little tricky>
The first part looks like:
Clock period & 0.4 & 1.0 \\
Same-CPU CAS & 12.2 & 33.8 \\
Same-CPU lock & 25.6 & 71.2 \\
Blind CAS & 12.9 & 35.8 \\
CAS & 7.0 & 19.4 \\
In this case, what would be the last lines "Blind CAS" and "CAS" referring to ?
(For a second I thought it could be "In-Core Blind CAS" and "In-Core CAS" like
in Table 3.1, but that would not make sense: This "CAS" is faster than the
previous "Same-CPU CAS". )
Thanks for reading,
Leo
next reply other threads:[~2023-02-08 3:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 3:07 Leonardo Brás [this message]
2023-02-08 3:41 ` Question about Table E.1 Paul E. McKenney
2023-02-08 5:33 ` Leonardo Brás
2023-02-08 5:50 ` Leonardo Brás
2023-02-08 8:47 ` Akira Yokosawa
2023-02-08 10:26 ` Akira Yokosawa
2023-02-08 22:15 ` Paul E. McKenney
2023-02-08 23:49 ` Akira Yokosawa
2023-02-09 11:13 ` Akira Yokosawa
2023-02-09 15:12 ` [PATCH -perfbook] cpu: PoC of A QQz citing table in answer to another QQz (was Re: Question about Table E.1) Akira Yokosawa
2023-02-11 8:49 ` Leonardo Brás
2023-02-12 0:04 ` Akira Yokosawa
2023-02-12 0:42 ` [PATCH -perfbook v2] cpu: Add a QQz on table E.1 Akira Yokosawa
2023-02-13 0:28 ` Paul E. McKenney
2023-02-13 1:54 ` Akira Yokosawa
2023-02-13 19:37 ` 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=fba1fe891b65449475c1e4e9abee2d3337c1567c.camel@gmail.com \
--to=leobras.c@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).