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] advsync/rt: Fold long list in \cite{}
Date: Sat, 17 Dec 2022 11:21:30 +0900 [thread overview]
Message-ID: <bd77b4d5-1be3-02b8-63b9-b97b15c03444@gmail.com> (raw)
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
Hi Paul,
You can break inside \cite{}.
This should be easier to maintain.
Thanks, Akira
---
advsync/rt.tex | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/advsync/rt.tex b/advsync/rt.tex
index 58dfc3224cb0..e9db1b04fc37 100644
--- a/advsync/rt.tex
+++ b/advsync/rt.tex
@@ -834,8 +834,13 @@ If configured properly, a non-trivial undertaking, \co{CONFIG_NO_HZ_FULL}
offers real-time threads levels of performance that come close to those of
bare-metal systems~\cite{AbdullahAljuhni2018nohzfull}.
\ppl{Fr\'{e}d\'{e}ric}{Weisbecker} produced a practical guide to
-\co{CONFIG_NO_HZ_FULL}
-configuration~\cite{FredericWeisbecker2022nohzIntro,FredericWeisbecker2022nohzFullDynticksInternals,FredericWeisbecker2022nohzfull,FredericWeisbecker2022HousekeepingTradeoffs,FredericWeisbecker2022practicalExample,FredericWeisbecker2022nohzfullTSC}.
+\co{CONFIG_NO_HZ_FULL} configuration~\cite{
+ FredericWeisbecker2022nohzIntro,
+ FredericWeisbecker2022nohzFullDynticksInternals,
+ FredericWeisbecker2022nohzfull,
+ FredericWeisbecker2022HousekeepingTradeoffs,
+ FredericWeisbecker2022practicalExample,
+ FredericWeisbecker2022nohzfullTSC}.
There has of course been much debate over which of these approaches
is best for real-time systems, and this debate has been going on for
base-commit: f59c468b212e66597c8f0c594839da53ccd1e949
--
2.25.1
next reply other threads:[~2022-12-17 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 2:21 Akira Yokosawa [this message]
2022-12-17 5:15 ` [PATCH -perfbook] advsync/rt: Fold long list in \cite{} 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=bd77b4d5-1be3-02b8-63b9-b97b15c03444@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).