From: patchwork-bot+netdevbpf@kernel.org
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
tj@kernel.org, jiangshanlai@gmail.com, frederic@kernel.org,
bigeasy@linutronix.de, mhocko@suse.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, chleroy@kernel.org, enelsonmoore@gmail.com,
haren@linux.ibm.com, maddy@linux.ibm.com, danishanwar@ti.com,
mpe@ellerman.id.au, westeri@kernel.org, mmc@linux.ibm.com,
npiggin@gmail.com, nnac123@linux.ibm.com, petkan@nucleusys.com,
icheng@nvidia.com, ricklind@linux.ibm.com, rogerq@kernel.org,
YehezkelShB@gmail.com
Subject: Re: [PATCH net-next v5 0/6] net: Move system_long_wq to system_dfl_long_wq
Date: Fri, 06 Nov 2026 21:10:07 +0000 [thread overview]
Message-ID: <179399940792.873414.7235430116859175660.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261102105703.111844-1-marco.crivellari@suse.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 2 Nov 2026 11:56:50 +0100 you wrote:
> Hello,
>
> Currently the code uses the per-cpu workqueue system_long_wq to schedule
> long running works.
>
> Unbound works could benefit from scheduler task placement, to optimize
> performance and power consumption. Another good reason to have this unbound,
> is the "queue_delayed_work()" function, used to enqueue the work item.
> More details on this will follow in the next section.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/6] ibmvnic: Change system_long_wq with system_dfl_long_wq
https://git.kernel.org/netdev/net-next/c/fc0f285bc191
- [net-next,v5,2/6] net: ti: icssg-stats: Move long delayed work on system_dfl_long_wq
https://git.kernel.org/netdev/net-next/c/d2ed709ff1e5
- [net-next,v5,3/6] net: ti: icssg-prueth: Move long delayed work on system_dfl_long_wq
https://git.kernel.org/netdev/net-next/c/12e337d448d1
- [net-next,v5,4/6] net: thunderbolt: Move long delayed work on system_dfl_long_wq
https://git.kernel.org/netdev/net-next/c/2adb5e4c7b40
- [net-next,v5,5/6] net: usb: pegasus: Move long delayed work on system_dfl_long_wq
https://git.kernel.org/netdev/net-next/c/733d1775cab0
- [net-next,v5,6/6] net: usb: r8152: Move long delayed work on system_dfl_long_wq
https://git.kernel.org/netdev/net-next/c/b3fcb84fdba4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-06 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 10:56 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
2026-11-06 21:10 ` patchwork-bot+netdevbpf [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=179399940792.873414.7235430116859175660.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=YehezkelShB@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=chleroy@kernel.org \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=frederic@kernel.org \
--cc=haren@linux.ibm.com \
--cc=icheng@nvidia.com \
--cc=jiangshanlai@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=mmc@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=nnac123@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pabeni@redhat.com \
--cc=petkan@nucleusys.com \
--cc=ricklind@linux.ibm.com \
--cc=rogerq@kernel.org \
--cc=tj@kernel.org \
--cc=westeri@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®