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 2/2] Documentation: btrfs: Document the influence of wq_cpu_set to thread_pool option
Date: Sun, 26 Feb 2023 23:26:39 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
If wq_cpu_set option is set, the default thread_pool value will be
adjusted accordingly.
Signed-off-by: Ammar Faizi <[email protected]>
---
Documentation/ch-mount-options.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/ch-mount-options.rst b/Documentation/ch-mount-options.rst
index 48fe63ee5e95c297..c38caf5e5fd0b719 100644
--- a/Documentation/ch-mount-options.rst
+++ b/Documentation/ch-mount-options.rst
@@ -411,6 +411,9 @@ thread_pool=<number>
due to increased locking contention, process scheduling, cache-line bouncing or
costly data transfers between local CPU memories.
+ Since 6.5, if *wq_cpu_set* is set, the default value will be the number of
+ online CPUs in the CPU wq_cpu_set plus 2.
+
treelog, notreelog
(default: on)
--
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 ` [RFC PATCH v1 1/2] Documentation: btrfs: Document wq_cpu_set mount option Ammar Faizi
2023-02-27 2:24 ` Bagas Sanjaya
2023-02-27 10:12 ` Ammar Faizi
2023-02-26 16:26 ` Ammar Faizi [this message]
2023-02-27 2:15 ` [RFC PATCH v1 2/2] Documentation: btrfs: Document the influence of wq_cpu_set to thread_pool option 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