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 1/2] memorder: Put \FloatBarrier in front of Section 15.3
Date: Wed, 28 Sep 2022 23:28:53 +0900 [thread overview]
Message-ID: <c8ec96f6-f592-36be-3d8a-55030d430caa@gmail.com> (raw)
Commit e39bbe1b0856 ("memorder: Add example showing store breaking
release-acquire chain") added a couple of code snippets in the
final subsection of Section 15.2.
In 1c builds, this caused the beginning part of Section 15.3 to
appear in the middle of floating code snippets of Section 15.2.
This can be prevented by putting \FloatBarrier in front of Section
15.3, with a (somewhat) wide vertical space left at the end of
Section 15.2.
Note: \FloatBarrier does nothing unless there are some overloaded
float objects. Therefore, 2c and eb builds are not affected.
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
Hi Paul,
Another option would be to use the "section" option of "placeins"
packages as is done for eb builds. I tried but I got quite a few
sparse-looking pages in other part of 1c builds. So I think adding
a \FloatBarrier here is a reasonable thing to do.
Thanks, Akira
--
memorder/memorder.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index 66f75662f26c..f85cfe6ca702 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -2404,6 +2404,8 @@ sea of more complex memory-ordering constraints.
% @@@ Exercises?
% @@@ Hardware details from Appendix?
+\FloatBarrier
+
\section{Compile-Time Consternation}
\label{sec:memorder:Compile-Time Consternation}
%
base-commit: 43d8aa12c84c8b26ffdb8479b4d793cc0159030e
--
2.25.1
next reply other threads:[~2022-09-28 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 14:28 Akira Yokosawa [this message]
2022-09-28 14:30 ` [PATCH -perfbook 2/2] memorder: Fix typo Akira Yokosawa
2022-09-28 17:46 ` 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=c8ec96f6-f592-36be-3d8a-55030d430caa@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).