From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 2/2] advsync/rt: Mention the tree of Documentation/ directory
Date: Sun, 11 Jun 2023 10:15:06 -0700 [thread overview]
Message-ID: <20230611171506.32033-3-sj@kernel.org> (raw)
In-Reply-To: <20230611171506.32033-1-sj@kernel.org>
From: SeongJae Park <sj38.park@gmail.com>
A sentence in rt.tex is mentioning a file under Linux source tree's
Documentation/ directory without the explanation of the tree. Add it so
that readers can easily find the mentioned file.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
advsync/rt.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/advsync/rt.tex b/advsync/rt.tex
index 5bcdfabc..e02da57a 100644
--- a/advsync/rt.tex
+++ b/advsync/rt.tex
@@ -1626,7 +1626,7 @@ real-time and heavy-compute workloads, but hurts other workloads
that feature high rates of system calls and
I/O~\cite{AbdullahAljuhni2018nohzfull}.
Additional limitations, tradeoffs, and configuration advice may be
-found in \path{Documentation/timers/no_hz.rst}.
+found in \path{Documentation/timers/no_hz.rst} file in the Linux source tree.
As you can see, obtaining bare-metal performance when running
CPU-bound real-time threads on a general-purpose OS such as Linux
--
2.17.1
next prev parent reply other threads:[~2023-06-11 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 17:15 [PATCH 0/2] advsync: Minor fixups SeongJae Park
2023-06-11 17:15 ` [PATCH 1/2] advsync/rt: Update path to kernel-per-CPU-kthreads document SeongJae Park
2023-06-11 17:15 ` SeongJae Park [this message]
2023-06-11 20:04 ` [PATCH 0/2] advsync: Minor fixups 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=20230611171506.32033-3-sj@kernel.org \
--to=sj@kernel.org \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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.