mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@ieee.org>
To: Tejun Heo <tj@kernel.org>, jiangshanlai@gmail.com
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	greybus-dev@lists.linaro.org
Subject: Re: [PATCH 02/22] greybus: Use alloc_ordered_workqueue() to create ordered workqueues
Date: Fri, 21 Apr 2023 03:15:56 -0500	[thread overview]
Message-ID: <57f311ec-381a-e468-3b28-bd73521d5e00@ieee.org> (raw)
In-Reply-To: <20230421025046.4008499-3-tj@kernel.org>

On 4/20/23 9:50 PM, Tejun Heo wrote:
> BACKGROUND
> ==========
> 
> When multiple work items are queued to a workqueue, their execution order
> doesn't match the queueing order. They may get executed in any order and
> simultaneously. When fully serialized execution - one by one in the queueing
> order - is needed, an ordered workqueue should be used which can be created
> with alloc_ordered_workqueue().
> 
> However, alloc_ordered_workqueue() was a later addition. Before it, an
> ordered workqueue could be obtained by creating an UNBOUND workqueue with
> @max_active==1. This originally was an implementation side-effect which was
> broken by 4c16bd327c74 ("workqueue: restore WQ_UNBOUND/max_active==1 to be
> ordered"). Because there were users that depended on the ordered execution,
> 5c0338c68706 ("workqueue: restore WQ_UNBOUND/max_active==1 to be ordered")
> made workqueue allocation path to implicitly promote UNBOUND workqueues w/
> @max_active==1 to ordered workqueues.
> 
> While this has worked okay, overloading the UNBOUND allocation interface
> this way creates other issues. It's difficult to tell whether a given
> workqueue actually needs to be ordered and users that legitimately want a
> min concurrency level wq unexpectedly gets an ordered one instead. With
> planned UNBOUND workqueue updates to improve execution locality and more
> prevalence of chiplet designs which can benefit from such improvements, this
> isn't a state we wanna be in forever.
> 
> This patch series audits all callsites that create an UNBOUND workqueue w/
> @max_active==1 and converts them to alloc_ordered_workqueue() as necessary.
> 
> WHAT TO LOOK FOR
> ================
> 
> The conversions are from
> 
>    alloc_workqueue(WQ_UNBOUND | flags, 1, args..)
> 
> to
> 
>    alloc_ordered_workqueue(flags, args...)
> 
> which don't cause any functional changes. If you know that fully ordered
> execution is not ncessary, please let me know. I'll drop the conversion and
> instead add a comment noting the fact to reduce confusion while conversion
> is in progress.
> 
> If you aren't fully sure, it's completely fine to let the conversion
> through. The behavior will stay exactly the same and we can always
> reconsider later.
> 
> As there are follow-up workqueue core changes, I'd really appreciate if the
> patch can be routed through the workqueue tree w/ your acks. Thanks.

Both of the workqueues affected here should be ordered.

Acked-by: Alex Elder <elder@linaro.org>

> 
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Johan Hovold <johan@kernel.org>
> Cc: Alex Elder <elder@kernel.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: greybus-dev@lists.linaro.org
> ---
>   drivers/greybus/connection.c | 4 ++--
>   drivers/greybus/svc.c        | 2 +-
>   2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/greybus/connection.c b/drivers/greybus/connection.c
> index e3799a53a193..9c88861986c8 100644
> --- a/drivers/greybus/connection.c
> +++ b/drivers/greybus/connection.c
> @@ -187,8 +187,8 @@ _gb_connection_create(struct gb_host_device *hd, int hd_cport_id,
>   	spin_lock_init(&connection->lock);
>   	INIT_LIST_HEAD(&connection->operations);
>   
> -	connection->wq = alloc_workqueue("%s:%d", WQ_UNBOUND, 1,
> -					 dev_name(&hd->dev), hd_cport_id);
> +	connection->wq = alloc_ordered_workqueue("%s:%d", 0, dev_name(&hd->dev),
> +						 hd_cport_id);
>   	if (!connection->wq) {
>   		ret = -ENOMEM;
>   		goto err_free_connection;
> diff --git a/drivers/greybus/svc.c b/drivers/greybus/svc.c
> index 16cced80867a..0d7e749174a4 100644
> --- a/drivers/greybus/svc.c
> +++ b/drivers/greybus/svc.c
> @@ -1318,7 +1318,7 @@ struct gb_svc *gb_svc_create(struct gb_host_device *hd)
>   	if (!svc)
>   		return NULL;
>   
> -	svc->wq = alloc_workqueue("%s:svc", WQ_UNBOUND, 1, dev_name(&hd->dev));
> +	svc->wq = alloc_ordered_workqueue("%s:svc", 0, dev_name(&hd->dev));
>   	if (!svc->wq) {
>   		kfree(svc);
>   		return NULL;


  parent reply	other threads:[~2023-04-21  8:16 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 [this message]
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
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=57f311ec-381a-e468-3b28-bd73521d5e00@ieee.org \
    --to=elder@ieee.org \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=jiangshanlai@gmail.com \
    --cc=johan@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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®