From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 1/2] advsync/rt: Update path to kernel-per-CPU-kthreads document
Date: Sun, 11 Jun 2023 10:15:05 -0700 [thread overview]
Message-ID: <20230611171506.32033-2-sj@kernel.org> (raw)
In-Reply-To: <20230611171506.32033-1-sj@kernel.org>
From: SeongJae Park <sj38.park@gmail.com>
Linux commit 4f4cfa6c560c ("docs: admin-guide: add a series of orphaned
documents") has moved Documentation/kernel-per-CPU-kthreads.txt to
Documentation/admin-guide/kernel-per-CPU-kthreads.rst. Update the old
path in advsync/rt.tex.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
advsync/rt.tex | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/advsync/rt.tex b/advsync/rt.tex
index c4d9c3c2..5bcdfabc 100644
--- a/advsync/rt.tex
+++ b/advsync/rt.tex
@@ -1486,7 +1486,8 @@ initiation take place on housekeeping CPUs, that special kernel
Kconfig or boot parameters be selected in order to direct work away from
the worker CPUs, or that worker CPUs never enter the kernel.
Specific per-kthread advice may be found in the Linux kernel source
-\path{Documentation} directory at \path{kernel-per-CPU-kthreads.txt}.
+\path{Documentation} directory at
+\path{admin-guide/kernel-per-CPU-kthreads.rst}.
A third source of OS jitter in the Linux kernel for CPU-bound threads
running at real-time priority is the scheduler itself.
--
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 ` SeongJae Park [this message]
2023-06-11 17:15 ` [PATCH 2/2] advsync/rt: Mention the tree of Documentation/ directory SeongJae Park
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-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox