From: "Michael S. Tsirkin" <mst@redhat.com>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>,
David Hildenbrand <david@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Eugenio Perez <eperezma@redhat.com>
Subject: Re: [PATCH 0/2] add WQ_PERCPU to alloc_workqueue() in virtio_balloon and vduse
Date: Mon, 17 Nov 2025 05:16:58 -0500 [thread overview]
Message-ID: <20251117051617-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20251107154917.313090-1-marco.crivellari@suse.com>
On Fri, Nov 07, 2025 at 04:49:15PM +0100, Marco Crivellari wrote:
> Hi,
>
> === Current situation: problems ===
>
> Let's consider a nohz_full system with isolated CPUs: wq_unbound_cpumask is
> set to the housekeeping CPUs, for !WQ_UNBOUND the local CPU is selected.
>
> This leads to different scenarios if a work item is scheduled on an
> isolated CPU where "delay" value is 0 or greater then 0:
> schedule_delayed_work(, 0);
>
> This will be handled by __queue_work() that will queue the work item on the
> current local (isolated) CPU, while:
>
> schedule_delayed_work(, 1);
>
> Will move the timer on an housekeeping CPU, and schedule the work there.
>
> Currently if a user enqueue a work item using schedule_delayed_work() the
> used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use
> WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to
> schedule_work() that is using system_wq and queue_work(), that makes use
> again of WORK_CPU_UNBOUND.
>
> This lack of consistency cannot be addressed without refactoring the API.
>
> === Recent changes to the WQ API ===
>
> The following, address the recent changes in the Workqueue API:
>
> - commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
> - commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
>
> The old workqueues will be removed in a future release cycle.
>
> === Introduced Changes by this series ===
>
> 1) [P 1-2] WQ_PERCPU added to alloc_workqueue()
>
> This adds a new WQ_PERCPU flag to explicitly request alloc_workqueue()
> to be per-cpu when WQ_UNBOUND has not been specified.
>
> Thanks!
>
> Marco Crivellari (2):
> virtio_balloon: add WQ_PERCPU to alloc_workqueue users
> vduse: add WQ_PERCPU to alloc_workqueue users
To make sure, this does not seem to introduce any
functional change - you want me to queue this now?
> drivers/vdpa/vdpa_user/vduse_dev.c | 3 ++-
> drivers/virtio/virtio_balloon.c | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> --
> 2.51.1
next prev parent reply other threads:[~2025-11-17 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 15:49 [PATCH 0/2] add WQ_PERCPU to alloc_workqueue() in virtio_balloon and vduse Marco Crivellari
2025-11-07 15:49 ` [PATCH 1/2] virtio_balloon: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2025-11-07 15:49 ` [PATCH 2/2] vduse: " Marco Crivellari
2025-11-17 10:16 ` Michael S. Tsirkin [this message]
2025-11-17 10:20 ` [PATCH 0/2] add WQ_PERCPU to alloc_workqueue() in virtio_balloon and vduse Marco Crivellari
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=20251117051617-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=david@redhat.com \
--cc=eperezma@redhat.com \
--cc=frederic@kernel.org \
--cc=jasowang@redhat.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=tj@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.