From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
Marcos Paulo de Souza <marcos.souza.org@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 4/4] Documentation:kernel-per-CPU-kthreads.txt: Remove reference to elevator=
Date: Sun, 14 Jul 2019 02:34:53 -0300 [thread overview]
Message-ID: <20190714053453.1655-5-marcos.souza.org@gmail.com> (raw)
In-Reply-To: <20190714053453.1655-1-marcos.souza.org@gmail.com>
This argument was not being considered since blk-mq was set by default,
so removed this documentation to avoid confusion.
Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
---
Documentation/kernel-per-CPU-kthreads.txt | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/Documentation/kernel-per-CPU-kthreads.txt b/Documentation/kernel-per-CPU-kthreads.txt
index 5623b9916411..c68c6c8c26a4 100644
--- a/Documentation/kernel-per-CPU-kthreads.txt
+++ b/Documentation/kernel-per-CPU-kthreads.txt
@@ -274,9 +274,7 @@ To reduce its OS jitter, do any of the following:
(based on an earlier one from Gilad Ben-Yossef) that
reduces or even eliminates vmstat overhead for some
workloads at https://lkml.org/lkml/2013/9/4/379.
- e. Boot with "elevator=noop" to avoid workqueue use by
- the block layer.
- f. If running on high-end powerpc servers, build with
+ e. If running on high-end powerpc servers, build with
CONFIG_PPC_RTAS_DAEMON=n. This prevents the RTAS
daemon from running on each CPU every second or so.
(This will require editing Kconfig files and will defeat
@@ -284,12 +282,12 @@ To reduce its OS jitter, do any of the following:
due to the rtas_event_scan() function.
WARNING: Please check your CPU specifications to
make sure that this is safe on your particular system.
- g. If running on Cell Processor, build your kernel with
+ f. If running on Cell Processor, build your kernel with
CBE_CPUFREQ_SPU_GOVERNOR=n to avoid OS jitter from
spu_gov_work().
WARNING: Please check your CPU specifications to
make sure that this is safe on your particular system.
- h. If running on PowerMAC, build your kernel with
+ g. If running on PowerMAC, build your kernel with
CONFIG_PMAC_RACKMETER=n to disable the CPU-meter,
avoiding OS jitter from rackmeter_do_timer().
--
2.22.0
next prev parent reply other threads:[~2019-07-14 5:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 5:34 [PATCH 0/4] Remove elevator kernel parameter Marcos Paulo de Souza
2019-07-14 5:34 ` [PATCH 1/4] block: elevator.c: Remove now unused elevator= argument Marcos Paulo de Souza
2019-07-19 13:36 ` Hannes Reinecke
2019-07-22 23:51 ` Bob Liu
2019-07-14 5:34 ` [PATCH 2/4] kernel-parameters.txt: Remove elevator argument Marcos Paulo de Souza
2019-07-19 13:36 ` Hannes Reinecke
2019-07-14 5:34 ` [PATCH 3/4] Documenation: switching-sched: Remove notes about " Marcos Paulo de Souza
2019-07-19 13:37 ` Hannes Reinecke
2019-07-14 5:34 ` Marcos Paulo de Souza [this message]
2019-07-19 13:37 ` [PATCH 4/4] Documentation:kernel-per-CPU-kthreads.txt: Remove reference to elevator= Hannes Reinecke
2019-07-25 20:04 ` [PATCH 0/4] Remove elevator kernel parameter Marcos Paulo de Souza
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=20190714053453.1655-5-marcos.souza.org@gmail.com \
--to=marcos.souza.org@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 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.