Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2x1GLtjAwppORlm12Cnq4C01NzR/rdVN5KspYEm0tNw=; b=fLK7plodAd261Lx6gUqJumVCuxD1VN8NASmx26QEF4BZMYuy9bJb9+bmi1tjqVpcNh jT6lAUK7EZ7o4yd71ED6Mzm2YAvYBhaH6hvZlIPHQXy1SOSEPCplocE6c0MYY2yvm7bA gg5h2wDHGY0BsWKq109RGUzylHMFARA6NfQbTFXN7x21brXIMujg+K9nxNQxOMlxlNC2 DRALNe7paGImfkDlyZMmtbKDCfV685SALFvAeVUuyYQrqYatcOA92C9baMVIa9bYj2Uq hHK0fJ/EsuixiJI/txrnS27iriCDw1Sz/FIaRB9b9ZQKiZoBtmlkOfI0YNe4bOf2rgfz wwxA== Subject: [PATCH 2/2] cpu/overheads: Typo fixes and wording improvement References: From: Akira Yokosawa Message-ID: <77c7810f-4a8d-811d-eddb-8fff92dafe65@gmail.com> Date: Wed, 11 Mar 2020 20:49:10 +0900 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit To: "Paul E. McKenney" Cc: perfbook@vger.kernel.org, Akira Yokosawa List-ID: From 9256445a646099df48b3f6af7ad232dd228f3039 Mon Sep 17 00:00:00 2001 From: Akira Yokosawa Date: Tue, 10 Mar 2020 22:12:45 +0900 Subject: [PATCH 2/2] cpu/overheads: Typo fixes and wording improvement Also flag suspicious raws in Table E.1 as comments. Signed-off-by: Akira Yokosawa --- Hi Paul, Think of this as a reminder rather than a patch to be applied as is. Updated Table E.1 looks inconsistent to me. Thanks, Akira -- cpu/overheads.tex | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/cpu/overheads.tex b/cpu/overheads.tex index d1b4f596..e5ea0803 100644 --- a/cpu/overheads.tex +++ b/cpu/overheads.tex @@ -189,7 +189,7 @@ atomic operations on the lock data structure, one for acquisition and the other for release. In-core operations involving interactions between the hardware threads -sharing a single core are about the same cost and same-CPU operations. +sharing a single core are about the same cost as same-CPU operations. This should not be too surprising, given that these two hardware threads also share the full cache hierarchy. CAS stands for an atomic compare-and-swap operation, where the hardware @@ -198,9 +198,9 @@ compares the contents of the specified memory location to a specified in which case the CAS operation is said to have succeeded. If they compare unequal, the memory location keeps its (unexpected) value, and the CAS operation is said to have failed. -The operation is atomic is that the hardware guarantees that the memory +The operation is atomic in that the hardware guarantees that the memory location will not be changed between the compare and the store. -CAS functionality is provided by the x86 \co{lock;cmpxchg} instruction. +CAS functionality is provided by the \co{lock;cmpxchg} instruction on x86. In the case of the blind CAS, the software specifies the old value without looking at the memory location. @@ -317,15 +317,15 @@ thousand clock cycles. 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 \\ + Blind CAS & 12.9 & 35.8 \\ % CAS? + CAS & 7.0 & 19.4 \\ % Blind CAS? \midrule Off-Core & & \\ - Blind CAS & 31.2 & 86.6 \\ + Blind CAS & 31.2 & 86.6 \\ % Realy Blind? CAS & 31.2 & 86.5 \\ \midrule Off-Socket & & \\ - Blind CAS & 92.4 & 256.7 \\ + Blind CAS & 92.4 & 256.7 \\ % Realy Blind? CAS & 95.9 & 266.4 \\ \midrule Off-System & & \\ -- 2.17.1