From: Leon Romanovsky <leon@kernel.org>
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>, Zhu Yanjun <zyjzyj2000@gmail.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] RDMA/rxe: Replace use of system_unbound_wq with system_dfl_wq
Date: Tue, 17 Mar 2026 18:24:29 +0200 [thread overview]
Message-ID: <20260317162429.GA61385@unreal> (raw)
In-Reply-To: <CAAofZF61VPo8VAX8zXUZnY-ydDYAR0N0mN2egaeTzXbiaKQbDw@mail.gmail.com>
On Tue, Mar 17, 2026 at 03:32:01PM +0100, Marco Crivellari wrote:
> On Mon, Mar 16, 2026 at 9:13 PM Leon Romanovsky <leon@kernel.org> wrote:
> > [...]
> > I recall earlier efforts to replace system workqueues with per‑driver queues,
> > because unloading a driver forces a flush of the entire system workqueue,
> > which is undesirable for overall system behavior.
> >
> > Wouldn't it be better to introduce a local workqueue here and use that instead?
> >
> > Thanks
>
> Hi,
>
> There is only this wq here. But we can do so if needed, no problem.
>
> Where do you think is the most appropriate place for the workqueue struct
> declaration? Like `struct prefetch_mr_work` maybe?
>
> Do you have suggestions for an appropriate place to allocate the workqueue?
Actually, RXE already have one workqueue in rxe_alloc_wq(), just use it.
Thanks
>
> Thanks!
>
> --
>
> Marco Crivellari
>
> L3 Support Engineer
next prev parent reply other threads:[~2026-03-17 16:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 15:40 [PATCH] RDMA/rxe: Replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2026-03-13 17:49 ` yanjun.zhu
2026-03-16 20:13 ` Leon Romanovsky
2026-03-17 14:32 ` Marco Crivellari
2026-03-17 16:24 ` Leon Romanovsky [this message]
2026-03-18 8:34 ` Marco Crivellari
2026-03-18 12:20 ` Marco Crivellari
2026-03-18 14:47 ` Zhu Yanjun
2026-03-18 15:02 ` Leon Romanovsky
2026-03-18 15:08 ` Marco Crivellari
2026-03-17 14:38 ` Zhu Yanjun
2026-03-17 17:24 ` Yanjun.Zhu
2026-03-17 19:03 ` Leon Romanovsky
2026-03-17 19:31 ` Yanjun.Zhu
2026-03-17 20:15 ` Yanjun.Zhu
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=20260317162429.GA61385@unreal \
--to=leon@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jiangshanlai@gmail.com \
--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=zyjzyj2000@gmail.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