From: Jason Gunthorpe <jgg@ziepe.ca>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
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>, Leon Romanovsky <leon@kernel.org>,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH 0/5] replaced system_unbound_wq, added WQ_PERCPU to alloc_workqueue
Date: Tue, 2 Dec 2025 15:17:52 -0400 [thread overview]
Message-ID: <20251202191752.GJ812105@ziepe.ca> (raw)
In-Reply-To: <CAAofZF7o+hA18Eiw=F9jbXBkeFqiw__eRx74Wb41EeTE1KP5PA@mail.gmail.com>
On Tue, Dec 02, 2025 at 02:22:55PM +0100, Marco Crivellari wrote:
> Hi,
>
> On Sat, Nov 1, 2025 at 5:31 PM Marco Crivellari
> <marco.crivellari@suse.com> wrote:
> > Marco Crivellari (5):
> > RDMA/core: RDMA/mlx5: replace use of system_unbound_wq with
> > system_dfl_wq
> > RDMA/core: WQ_PERCPU added to alloc_workqueue users
> > hfi1: WQ_PERCPU added to alloc_workqueue users
> > RDMA/mlx4: WQ_PERCPU added to alloc_workqueue users
> > IB/rdmavt: WQ_PERCPU added to alloc_workqueue users
> >
> > drivers/infiniband/core/cm.c | 2 +-
> > drivers/infiniband/core/device.c | 4 ++--
> > drivers/infiniband/core/ucma.c | 2 +-
> > drivers/infiniband/hw/hfi1/init.c | 4 ++--
> > drivers/infiniband/hw/hfi1/opfn.c | 4 ++--
> > drivers/infiniband/hw/mlx4/cm.c | 2 +-
> > drivers/infiniband/hw/mlx5/odp.c | 4 ++--
> > drivers/infiniband/sw/rdmavt/cq.c | 3 ++-
> > 8 files changed, 13 insertions(+), 12 deletions(-)
>
> Gentle ping.
It looks like it was picked up, the thank you email must have become lost:
5c467151f6197d IB/isert: add WQ_PERCPU to alloc_workqueue users
65d21dee533755 IB/iser: add WQ_PERCPU to alloc_workqueue users
7196156b0ce3dc IB/rdmavt: WQ_PERCPU added to alloc_workqueue users
5267feda50680c RDMA/mlx4: WQ_PERCPU added to alloc_workqueue users
5f93287fa9d0db hfi1: WQ_PERCPU added to alloc_workqueue users
e60c5583b661da RDMA/core: WQ_PERCPU added to alloc_workqueue users
f673fb3449fcd8 RDMA/core: RDMA/mlx5: replace use of system_unbound_wq with system_dfl_wq
Jason
next prev parent reply other threads:[~2025-12-02 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 16:31 [PATCH 0/5] replaced system_unbound_wq, added WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-11-01 16:31 ` [PATCH 1/5] RDMA/core: RDMA/mlx5: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-11-01 16:31 ` [PATCH 2/5] RDMA/core: WQ_PERCPU added to alloc_workqueue users Marco Crivellari
2025-11-01 16:31 ` [PATCH 3/5] hfi1: " Marco Crivellari
2025-11-01 16:31 ` [PATCH 4/5] RDMA/mlx4: " Marco Crivellari
2025-11-01 16:31 ` [PATCH 5/5] IB/rdmavt: " Marco Crivellari
2025-12-02 13:22 ` [PATCH 0/5] replaced system_unbound_wq, added WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-12-02 19:17 ` Jason Gunthorpe [this message]
2025-12-03 13:46 ` 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=20251202191752.GJ812105@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bigeasy@linutronix.de \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=tj@kernel.org \
--cc=yishaih@nvidia.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