From: John Pittman <jpittman@redhat.com>
To: paolo.valente@linaro.org
Cc: axboe@kernel.dk, corbet@lwn.net, linux-block@vger.kernel.org,
linux-doc@vger.kernel.org, John Pittman <jpittman@redhat.com>
Subject: [PATCH] block: doc: add slice_idle_us to bfq documentation
Date: Tue, 8 Jan 2019 16:56:13 -0500 [thread overview]
Message-ID: <20190108215613.15277-1-jpittman@redhat.com> (raw)
Of the tunables available for the bfq I/O scheduler,
the only one missing from the documentation in
'Documentation/block/bfq-iosched.txt' is slice_idle_us.
Add this tunable to the documentation and a short
explanation of its purpose.
Signed-off-by: John Pittman <jpittman@redhat.com>
---
Documentation/block/bfq-iosched.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/block/bfq-iosched.txt b/Documentation/block/bfq-iosched.txt
index 8d8d8f06cab2..98a8dd5ee385 100644
--- a/Documentation/block/bfq-iosched.txt
+++ b/Documentation/block/bfq-iosched.txt
@@ -357,6 +357,13 @@ video playing/streaming, a very low drop rate may be more important
than maximum throughput. In these cases, consider setting the
strict_guarantees parameter.
+slice_idle_us
+-------------
+
+Controls the same tuning parameter as slice_idle, but in microseconds.
+Either tunable can be used to set idling behavior. Afterwards, the
+other tunable will reflect the newly set value in sysfs.
+
strict_guarantees
-----------------
--
2.17.2
next reply other threads:[~2019-01-08 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 21:56 John Pittman [this message]
2019-01-09 6:08 ` [PATCH] block: doc: add slice_idle_us to bfq documentation Paolo Valente
2019-01-09 14:39 ` Jens Axboe
2019-01-09 15:16 ` John Pittman
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=20190108215613.15277-1-jpittman@redhat.com \
--to=jpittman@redhat.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=paolo.valente@linaro.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