From: Simon Horman <horms@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, netdev@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>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ethan Nelson-Moore <enelsonmoore@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next v5 6/6] net: usb: r8152: Move long delayed work on system_dfl_long_wq
Date: Thu, 5 Nov 2026 20:32:58 +0000 [thread overview]
Message-ID: <20261105203258.GA865646@horms.kernel.org> (raw)
In-Reply-To: <20261102105703.111844-7-marco.crivellari@suse.com>
On Mon, Nov 02, 2026 at 11:56:56AM +0100, Marco Crivellari wrote:
> Currently the code enqueue work items using {queue|mod}_delayed_work(),
> using system_long_wq. This workqueue should be used when long works are
> expected and it is a per-cpu workqueue.
>
> The function(s) end up calling __queue_delayed_work(), which set a global
> timer that could fire anywhere, enqueuing the work where the timer fired.
>
> Unbound works could benefit from scheduler task placement, to optimize
> performance and power consumption. Long work shouldn't stick to a single
> CPU.
>
> Recently, a new unbound workqueue specific for long running work has
> been added:
>
> c116737e972e ("workqueue: Add system_dfl_long_wq for long unbound works")
>
> Since the workqueue work doesn't rely on per-cpu variables, there is no
> obvious reason that justify the use of a per-cpu workqueue. So change
> system_long_wq with system_dfl_long_wq so that the work may benefit from
> scheduler task placement.
>
> Cc: Ethan Nelson-Moore <enelsonmoore@gmail.com>
> Cc: linux-usb@vger.kernel.org
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2026-11-05 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 10:56 [PATCH net-next v5 0/6] net: Move system_long_wq to system_dfl_long_wq Marco Crivellari
2026-11-02 10:56 ` [PATCH net-next v5 1/6] ibmvnic: Change system_long_wq with system_dfl_long_wq Marco Crivellari
2026-11-02 10:56 ` [PATCH net-next v5 2/6] net: ti: icssg-stats: Move long delayed work on system_dfl_long_wq Marco Crivellari
2026-11-02 10:56 ` [PATCH net-next v5 3/6] net: ti: icssg-prueth: " Marco Crivellari
2026-11-05 20:32 ` Simon Horman
2026-11-02 10:56 ` [PATCH net-next v5 4/6] net: thunderbolt: " Marco Crivellari
2026-11-02 10:56 ` [PATCH net-next v5 5/6] net: usb: pegasus: " Marco Crivellari
2026-11-02 10:56 ` [PATCH net-next v5 6/6] net: usb: r8152: " Marco Crivellari
2026-11-05 20:32 ` Simon Horman [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=20261105203258.GA865646@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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®