From: Waiman Long <longman@redhat.com>
To: Lai Jiangshan <jiangshanlai@gmail.com>, linux-kernel@vger.kernel.org
Cc: Lai Jiangshan <jiangshan.ljs@antgroup.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] workqueue: Always queue work items to the newest PWQ for order workqueues
Date: Wed, 3 Jul 2024 14:06:12 -0400 [thread overview]
Message-ID: <c9c9ed1c-116d-4deb-b54e-6e464c342f23@redhat.com> (raw)
In-Reply-To: <20240703092741.22997-1-jiangshanlai@gmail.com>
On 7/3/24 05:27, Lai Jiangshan wrote:
> From: Lai Jiangshan <jiangshan.ljs@antgroup.com>
>
> To ensure non-reentrancy, __queue_work() attempts to enqueue a work
> item to the pool of the currently executing worker. This is not only
> unnecessary for an ordered workqueue, where order inherently suggests
> non-reentrancy, but it could also disrupt the sequence if the item is
> not enqueued on the newest PWQ.
>
> Just queue it to the newest PWQ and let order management guarantees
> non-reentrancy.
>
> Fixes: 4c065dbce1e8("workqueue: Enable unbound cpumask update on ordered workqueues")
> Signed-off-by: Lai Jiangshan <jiangshan.ljs@antgroup.com>
> ---
> kernel/workqueue.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index c910f3c28664..d4fecd23ea44 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -2271,9 +2271,13 @@ static void __queue_work(int cpu, struct workqueue_struct *wq,
> * If @work was previously on a different pool, it might still be
> * running there, in which case the work needs to be queued on that
> * pool to guarantee non-reentrancy.
> + *
> + * For ordered workqueue, work items must be queued on the newest pwq
> + * for accurate order management. Guaranteed order also guarantees
> + * non-reentrancy. See the comments above unplug_oldest_pwq().
> */
> last_pool = get_work_pool(work);
> - if (last_pool && last_pool != pool) {
> + if (last_pool && last_pool != pool && !(wq->flags & __WQ_ORDERED)) {
> struct worker *worker;
>
> raw_spin_lock(&last_pool->lock);
Thanks for the fix again.
Acked-by: Waiman Long <longman@redhat.com>
prev parent reply other threads:[~2024-07-03 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 9:27 Lai Jiangshan
2024-07-03 17:40 ` Tejun Heo
2024-07-03 18:06 ` Waiman Long [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=c9c9ed1c-116d-4deb-b54e-6e464c342f23@redhat.com \
--to=longman@redhat.com \
--cc=jiangshan.ljs@antgroup.com \
--cc=jiangshanlai@gmail.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®