From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, fw@strlen.de, horms@kernel.org
Subject: Re: [PATCH net-next 1/7] ipvs: Move defense_work and est_reload_work to system_dfl_long_wq
Date: Tue, 28 Jul 2026 01:10:25 +0000 [thread overview]
Message-ID: <178520102513.1486027.6830944309347265032.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260724104932.437729-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Fri, 24 Jul 2026 12:49:26 +0200 you wrote:
> From: Ismael Luceno <iluceno@suse.de>
>
> Under synflood conditions binding these handlers to system_long_wq may
> pin them to a saturated CPU.
>
> We've observed improved throughtput on a DPDK/VPP application with this
> change, which we attribute to the reduced context switching.
>
> [...]
Here is the summary with links:
- [net-next,1/7] ipvs: Move defense_work and est_reload_work to system_dfl_long_wq
https://git.kernel.org/netdev/net-next/c/0a33bdce34c6
- [net-next,2/7] netfilter: xt_tcpmss: extend checkentry to ipv6
https://git.kernel.org/netdev/net-next/c/4172fd3697b0
- [net-next,3/7] netfilter: nf_nat_sip: rewind offset when NAT shrinks the packet
https://git.kernel.org/netdev/net-next/c/16aecbe3036f
- [net-next,4/7] netfilter: flowtable: tear down flow entries with stale dst from GC
https://git.kernel.org/netdev/net-next/c/edd51a233438
- [net-next,5/7] netfilter: conntrack_helper: pass master conntrack to helper functions
https://git.kernel.org/netdev/net-next/c/1c66ad76ddd4
- [net-next,6/7] netfilter: nf_conntrack_expect: store event cache in expectation
https://git.kernel.org/netdev/net-next/c/874f455c3a29
- [net-next,7/7] ipvs: use type-safe allocation helpers in ip_vs_rht_alloc
https://git.kernel.org/netdev/net-next/c/cca2780b6194
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-07-28 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 10:49 [PATCH net-next 0/7] Netfilter/IPVS updates for net-next Pablo Neira Ayuso
2026-07-24 10:49 ` [PATCH net-next 1/7] ipvs: Move defense_work and est_reload_work to system_dfl_long_wq Pablo Neira Ayuso
2026-07-28 1:10 ` patchwork-bot+netdevbpf [this message]
2026-07-24 10:49 ` [PATCH net-next 2/7] netfilter: xt_tcpmss: extend checkentry to ipv6 Pablo Neira Ayuso
2026-07-24 10:49 ` [PATCH net-next 3/7] netfilter: nf_nat_sip: rewind offset when NAT shrinks the packet Pablo Neira Ayuso
2026-07-24 10:49 ` [PATCH net-next 4/7] netfilter: flowtable: tear down flow entries with stale dst from GC Pablo Neira Ayuso
2026-07-24 10:49 ` [PATCH net-next 5/7] netfilter: conntrack_helper: pass master conntrack to helper functions Pablo Neira Ayuso
2026-07-24 10:49 ` [PATCH net-next 6/7] netfilter: nf_conntrack_expect: store event cache in expectation Pablo Neira Ayuso
2026-07-24 10:49 ` [PATCH net-next 7/7] ipvs: use type-safe allocation helpers in ip_vs_rht_alloc Pablo Neira Ayuso
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=178520102513.1486027.6830944309347265032.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.