From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Filipe Manana <fdmanana@suse.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Btrfs Mailing List <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fsdevel Mailing List <linux-fsdevel@vger.kernel.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: [RFC PATCH v1 0/2] Documentation: Introducing `wq_cpu_set` mount option for btrfs
Date: Sun, 26 Feb 2023 23:26:37 +0700 [thread overview]
Message-ID: <20230226162639.20559-1-ammarfaizi2@gnuweeb.org> (raw)
This is a follow up RFC of this series:
https://lore.kernel.org/linux-btrfs/20230226160259.18354-1-ammarfaizi2@gnuweeb.org
It contains the documentation for the `wq_cpu_set` mount option.
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
Ammar Faizi (2):
Documentation: btrfs: Document wq_cpu_set mount option
Documentation: btrfs: Document the influence of wq_cpu_set to thread_pool option
Documentation/ch-mount-options.rst | 32 ++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
base-commit: 908b4b4450320e30fdef693f09b42f4eb93702c3
--
Ammar Faizi
next 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 Ammar Faizi [this message]
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 ` [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 \
--in-reply-to=20230226162639.20559-1-ammarfaizi2@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=gwml@vger.gnuweeb.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®