Thread (19 messages) 19 messages, 6 authors, 22d ago

Re: [PATCH v3 net-next 5/6] net: usb: pegasus: Move long delayed work on system_dfl_long_wq

From: Petko Manolov <petkan@nucleusys.com>
Date: 2026-09-04 15:10:13
Also in: linux-usb, lkml

On 26-08-28 10:10:01, Alan Stern wrote:
On Fri, Aug 28, 2026 at 11:43:18AM +0200, Sebastian Andrzej Siewior wrote:
quoted
Therefore the suggested change system_long_wq -> system_dfl_long_wq should
not make a difference here: it is a different workqueue and it is unbound
(instead of per-CPU) but given the usage it is unchanged but more obvious.
Also its usage recommendations (use this for long running items) is the
same.

The plan is remove system_long_wq from the tree.
The point Oliver was making is that the driver shouldn't be using a
general-purpose workqueue at all.  Switching from one general-purpose
workqueue to another ignores this point; it's not the right thing to do.
I read this as "this driver should switch to its own work queue", correct?


		Petko
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help