From: Ammar Faizi <[email protected]>
To: Chris Mason <[email protected]>, Josef Bacik <[email protected]>,
David Sterba <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Filipe Manana <[email protected]>,
Linux Doc Mailing List <[email protected]>,
Linux Btrfs Mailing List <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
Linux Fsdevel Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: [RFC PATCH v1 1/2] Documentation: btrfs: Document wq_cpu_set mount option
Date: Sun, 26 Feb 2023 23:26:38 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Document a new Btrfs mount option, wq_cpu_set.
Signed-off-by: Ammar Faizi <[email protected]>
---
Documentation/ch-mount-options.rst | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/Documentation/ch-mount-options.rst b/Documentation/ch-mount-options.rst
index f0f205dc20fa15ff..48fe63ee5e95c297 100644
--- a/Documentation/ch-mount-options.rst
+++ b/Documentation/ch-mount-options.rst
@@ -451,6 +451,35 @@ user_subvol_rm_allowed
ordinary directory. Whether this is possible can be detected at runtime, see
*rmdir_subvol* feature in *FILESYSTEM FEATURES*.
+wq_cpu_set=<cpu_set>
+ (since: 6.5, default: all online CPUs)
+
+ Btrfs workqueues can slow sensitive user tasks down because they can use any
+ online CPU to perform heavy workloads on an SMP system. This option is used to
+ isolate the Btrfs workqueues to a set of CPUs. It is helpful to avoid
+ sensitive user tasks being preempted by Btrfs heavy workqueues.
+
+ The *cpu_set* is a dot-separated list of decimal numbers and ranges. The
+ numbers are CPU numbers, the ranges are inclusive. For example:
+
+ - *wq_cpu_set=0.3-7* will use CPUs 0, 3, 4, 5, 6 and 7.
+
+ - *wq_cpu_set=0.4.1.5* will use CPUs 0, 1, 4 and 5.
+
+ This option is similar to the taskset bitmask except that the comma separator
+ is replaced with a dot. The reason for this is that the mount option parser
+ uses commas to separate mount options.
+
+ If *wq_cpu_set* option is specificed and the *thread_pool* option is not, the
+ number of default max thread pool size will be set to the number of online
+ CPUs in the specified CPU set plus 2, if and only if the resulting number is
+ less than 8.
+
+ If *wq_cpu_set* option is specificed and the *thread_pool* option is also
+ specified, the thread pool size will be set to the value of *thread_pool*
+ option.
+
+
DEPRECATED MOUNT OPTIONS
^^^^^^^^^^^^^^^^^^^^^^^^
--
Ammar Faizi
next prev parent reply other threads:[~2023-02-26 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 16:26 [RFC PATCH v1 0/2] Documentation: Introducing `wq_cpu_set` mount option for btrfs Ammar Faizi
2023-02-26 16:26 ` Ammar Faizi [this message]
2023-02-27 2:24 ` [RFC PATCH v1 1/2] Documentation: btrfs: Document wq_cpu_set mount option Bagas Sanjaya
2023-02-27 10:12 ` Ammar Faizi
2023-02-26 16:26 ` [RFC PATCH v1 2/2] Documentation: btrfs: Document the influence of wq_cpu_set to thread_pool option Ammar Faizi
2023-02-27 2:15 ` Bagas Sanjaya
2023-02-27 10:02 ` Ammar Faizi
2023-03-01 2:06 ` Bagas Sanjaya
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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