From: Tejun Heo <tj@kernel.org>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
kernel-team@meta.com, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 16/22] btrfs: Use alloc_ordered_workqueue() to create ordered workqueues
Date: Mon, 8 May 2023 13:50:50 -1000 [thread overview]
Message-ID: <ZFmK2uV6n8cJ1ec0@slm.duckdns.org> (raw)
In-Reply-To: <20230506094013.29A6.409509F4@e16-tech.com>
On Sat, May 06, 2023 at 09:40:14AM +0800, Wang Yugui wrote:
> by test, I noticed some warning caused by
> void workqueue_set_max_active(struct workqueue_struct *wq, int max_active)
> if (WARN_ON(wq->flags & __WQ_ORDERED_EXPLICIT))
> return;
>
> so I tested again with the flowing fix
>
> diff --git a/fs/btrfs/async-thread.c b/fs/btrfs/async-thread.c
> index 43c8995..e4b68e9 100644
> --- a/fs/btrfs/async-thread.c
> +++ b/fs/btrfs/async-thread.c
> @@ -99,8 +99,11 @@ struct btrfs_workqueue *btrfs_alloc_workqueue(struct btrfs_fs_info *fs_info,
> ret->thresh = thresh;
> }
>
> - ret->normal_wq = alloc_workqueue("btrfs-%s", flags, ret->current_active,
> - name);
> + if(limit_active == 1)
> + ret->normal_wq = alloc_ordered_workqueue("btrfs-%s", flags, name);
> + else
> + ret->normal_wq = alloc_workqueue("btrfs-%s", flags,
> + ret->current_active, name);
> if (!ret->normal_wq) {
> kfree(ret);
> return NULL;
> @@ -139,7 +139,7 @@ static inline void thresh_exec_hook(struct btrfs_workqueue *wq)
> long pending;
> int need_change = 0;
>
> - if (wq->thresh == NO_THRESHOLD)
> + if (wq->thresh == NO_THRESHOLD || wq->limit_active == 1)
> return;
>
> atomic_dec(&wq->pending);
>
> we need 'limit_active' at 2nd postition, so I used 'limit_active' and 1st
> postition too.
Oh, that most likely means that these workqueues don't need to and shouldn't
be ordered. Will update the patch.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-05-08 23:50 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 2:50 [PATCHSET wq/for-6.5] workqueue: Ordered workqueue creation cleanup Tejun Heo
2023-04-21 2:50 ` [PATCH 01/22] powerpc, workqueue: Use alloc_ordered_workqueue() to create ordered workqueues Tejun Heo
2023-04-21 5:20 ` Michael Ellerman
2023-05-08 23:55 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 02/22] greybus: " Tejun Heo
2023-04-21 5:03 ` Greg Kroah-Hartman
2023-04-21 6:29 ` Johan Hovold
2023-04-21 8:15 ` Alex Elder
2023-05-08 23:55 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 03/22] IB/hfi1: " Tejun Heo
2023-04-21 14:02 ` Dennis Dalessandro
2023-05-08 23:56 ` Tejun Heo
2023-05-09 1:35 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 04/22] dm integrity: " Tejun Heo
2023-04-21 2:50 ` [PATCH 05/22] media: amphion: " Tejun Heo
2023-04-21 2:50 ` [PATCH 06/22] net: thunderx: " Tejun Heo
2023-04-21 6:19 ` [EXT] " Sunil Kovvuri Goutham
2023-04-21 14:01 ` Jakub Kicinski
2023-04-21 14:13 ` Tejun Heo
2023-04-21 14:28 ` Jakub Kicinski
2023-05-08 23:57 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 07/22] net: octeontx2: " Tejun Heo
2023-04-21 6:16 ` [EXT] " Sunil Kovvuri Goutham
2023-05-08 23:56 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 08/22] wifi: ath10/11/12k: " Tejun Heo
2023-04-21 2:50 ` [PATCH 09/22] wifi: iwlwifi: " Tejun Heo
2023-04-24 17:31 ` Johannes Berg
2023-05-05 22:52 ` [PATCH] wifi: iwlwifi: Use default @max_active for trans_pcie->rba.alloc_wq Tejun Heo
2023-05-08 16:05 ` Johannes Berg
2023-05-08 23:59 ` [PATCH 09/22] wifi: iwlwifi: Use alloc_ordered_workqueue() to create ordered workqueues Tejun Heo
2023-05-09 15:25 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 10/22] wifi: mwifiex: " Tejun Heo
2023-04-25 18:14 ` Brian Norris
2023-05-05 22:53 ` [PATCH] wifi: mwifiex: Use default @max_active for workqueues Tejun Heo
2023-04-21 2:50 ` [PATCH 11/22] net: wwan: t7xx: Use alloc_ordered_workqueue() to create ordered workqueues Tejun Heo
2023-04-21 2:50 ` [PATCH 12/22] scsi: " Tejun Heo
2023-04-21 14:23 ` Benjamin Block
2023-05-08 23:57 ` Tejun Heo
2023-05-09 1:22 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 13/22] virt: acrn: " Tejun Heo
2023-04-21 5:03 ` Greg Kroah-Hartman
2023-05-08 23:58 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 14/22] soc: qcom: qmi: " Tejun Heo
2023-04-21 2:50 ` [PATCH 15/22] xen/pvcalls: " Tejun Heo
2023-05-08 11:58 ` Juergen Gross
2023-05-08 23:59 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 16/22] btrfs: " Tejun Heo
2023-04-30 4:40 ` Wang Yugui
2023-05-05 22:58 ` [PATCH v2 " Tejun Heo
2023-05-06 1:40 ` Wang Yugui
2023-05-08 23:50 ` Tejun Heo [this message]
2023-04-21 2:50 ` [PATCH 17/22] cifs: " Tejun Heo
2023-04-21 18:38 ` Paulo Alcantara
2023-05-08 23:58 ` Tejun Heo
2023-04-21 2:50 ` [PATCH 18/22] net: qrtr: " Tejun Heo
2023-04-21 2:50 ` [PATCH 19/22] rxrpc: " Tejun Heo
2023-04-21 2:50 ` [PATCH 20/22] crypto: octeontx2: " Tejun Heo
2023-04-21 2:50 ` [PATCH 21/22] media: coda: " Tejun Heo
2023-04-21 2:50 ` [PATCH 22/22] workqueue: Don't implicitly make UNBOUND workqueues w/ @max_active==1 ordered Tejun Heo
2023-04-24 5:03 ` Christoph Hellwig
2023-05-25 4:54 ` (subset) [PATCHSET wq/for-6.5] workqueue: Ordered workqueue creation cleanup Bjorn Andersson
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=ZFmK2uV6n8cJ1ec0@slm.duckdns.org \
--to=tj@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jiangshanlai@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangyugui@e16-tech.com \
/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®