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 2/2] defer: Use \tco{} in inline enum list
Date: Thu, 9 May 2024 00:18:45 +0900 [thread overview]
Message-ID: <7c8a128e-b49c-41ff-be52-d05706cc878b@gmail.com> (raw)
In-Reply-To: <bc5fc6da-1f06-43b3-b065-3292652d78f8@gmail.com>
Using \co{} in list environments such as enumerate* can confuse
LeTeX engines in width estimation due to possible line breaks
therein.
It causes an overlap of "," over the closing ")" of "read_seqretry()"
in the answer to QQz 9.14.
Use \tco{} to avoid such undesired results.
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
defer/seqlock.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/defer/seqlock.tex b/defer/seqlock.tex
index 5be8ae56..3ed2f483 100644
--- a/defer/seqlock.tex
+++ b/defer/seqlock.tex
@@ -141,7 +141,7 @@ will pass to a later call to \co{read_seqretry()}.
\begin{enumerate*}[(1)]
\item This added check is a relatively expensive conditional branch,
\item It cannot be substituted for the later check done by
- \co{read_seqretry()}, which must happen after the
+ \tco{read_seqretry()}, which must happen after the
critical section completes, and
\item Sequence locking is intended for read-mostly workloads,
which means that this extra check would slow down the
--
2.34.1
next prev parent reply other threads:[~2024-05-08 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 15:16 [PATCH -perfbook 1/2] locking: Mark sentence-ending period as such Akira Yokosawa
2024-05-08 15:18 ` Akira Yokosawa [this message]
2024-05-08 17:39 ` 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=7c8a128e-b49c-41ff-be52-d05706cc878b@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 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).