All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH -perfbook 3/4] questions: Reference Tables 17.1 and 17.2 instead of Table 17.3 in -eb build
Date: Thu, 22 Apr 2021 00:29:06 +0900	[thread overview]
Message-ID: <401ad976-8bda-85d2-bffc-39369043e4eb@gmail.com> (raw)
In-Reply-To: <5a17ce08-9c5d-5e87-6cae-793c6a49c147@gmail.com>

As Table 17.3 (merged large table) is not available in -eb build due
to its size, reference Tables 17.1 and 17.2 instead.

Also use \cpageref{} for "page~\pageref{}".

Fixes: 2db0c0f61ea1 ("appendix/questions: Address and remove "@@@" todo flags, take two")
[conflicts with 1704b2b83177 ("treewide: Shrink floats for ebook-size build"),
whose change log mentions "Figure 17.3" meaning *Table* 17.3]
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
 appendix/questions/removelocking.tex | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/appendix/questions/removelocking.tex b/appendix/questions/removelocking.tex
index 6678e7a2..f87bdf41 100644
--- a/appendix/questions/removelocking.tex
+++ b/appendix/questions/removelocking.tex
@@ -19,9 +19,17 @@ Furthermore, as a general rule, the more complex the algorithm,
 the greater the advantage of combining locking with selected
 lockless techniques, even with significant hardware support,
 as shown in
+\IfEbookSize{
+\cref{tab:future:Comparison of Locking and HTM,%
+tab:future:Comparison of Locking (Augmented by RCU or Hazard Pointers) and HTM}
+on
+\cpageref{tab:future:Comparison of Locking and HTM,%
+tab:future:Comparison of Locking (Augmented by RCU or Hazard Pointers) and HTM}.
+}{
 \cref{tab:future:Comparison of Locking (Plain and Augmented) and HTM}
 on
-page~\pageref{tab:future:Comparison of Locking (Plain and Augmented) and HTM}.
+\cpageref{tab:future:Comparison of Locking (Plain and Augmented) and HTM}.
+}
 \Cref{sec:advsync:Non-Blocking Synchronization}
 looks more deeply at non-blocking synchronization, which is a popular
 lockless methodology.
-- 
2.17.1



  parent reply	other threads:[~2021-04-21 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 15:25 [PATCH -perfbook 0/4] index: Add index and acronym tags, take one Akira Yokosawa
2021-04-21 15:26 ` [PATCH -perfbook 1/4] synctex-forward: Update target list Akira Yokosawa
2021-04-21 15:27 ` [PATCH -perfbook 2/4] synctex-forward: Skip database check when reverting Akira Yokosawa
2021-04-21 15:29 ` Akira Yokosawa [this message]
2021-04-21 15:30 ` [PATCH -perfbook 4/4] index: Add index and acronym tags, take one Akira Yokosawa
2021-04-21 17:43 ` [PATCH -perfbook 0/4] " 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=401ad976-8bda-85d2-bffc-39369043e4eb@gmail.com \
    --to=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 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.