From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
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: Re: [RFC PATCH v1 2/2] Documentation: btrfs: Document the influence of wq_cpu_set to thread_pool option
Date: Wed, 1 Mar 2023 09:06:30 +0700 [thread overview]
Message-ID: <ac60affc-ac5c-2ee7-c1a6-9be39e7b43c9@gmail.com> (raw)
In-Reply-To: <Y/x/oD+byOu092fF@biznet-home.integral.gnuweeb.org>
On 2/27/23 17:02, Ammar Faizi wrote:
> On Mon, Feb 27, 2023 at 09:15:58AM +0700, Bagas Sanjaya wrote:
>> Why will the behavior be introduced in such future version (6.5)?
>
> It's not like it has been staged for the next merge window. It's still
> in an RFC state. The changes are not trivial and need further review.
>
> I don't know if it can hit the next merge window. As such, I picked a
> long distance for this proposal. If it ends up going upstream sooner, we
> can change this document.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-03-01 2:06 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 ` [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 [this message]
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=ac60affc-ac5c-2ee7-c1a6-9be39e7b43c9@gmail.com \
--to=bagasdotme@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).