From: Simon Horman <horms@kernel.org>
To: Ismael Luceno <iluceno@suse.de>
Cc: linux-kernel@vger.kernel.org, "Julian Anastasov" <ja@ssi.bg>,
"Pablo Neira Ayuso" <pablo@netfilter.org>,
"Florian Westphal" <fw@strlen.de>, "Phil Sutter" <phil@nwl.cc>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Marco Crivellari" <marco.crivellari@suse.com>,
"Federico Pinca" <federico.pinca@suse.com>,
"Andreas Taschner" <andreas.taschner@suse.com>,
"Brad Bendily" <brad.bendily@suse.com>,
"Brendon Caligari" <brendon.caligari@suse.com>,
"Clemens Famulla-Conrad" <cfamullaconrad@suse.com>,
"Firo Yang" <firo.yang@suse.com>,
"Gabriel Krisman Bertazi" <gabriel.bertazi@suse.com>,
"Hans van den Heuvel" <hvdheuvel@suse.com>,
"Jean Delvare" <jdelvare@suse.com>,
"Michal Hocko" <mhocko@suse.com>,
"Michal Koutný" <mkoutny@suse.com>,
"Petr Mladek" <pmladek@suse.com>,
"Petr Tesarik" <ptesarik@suse.com>,
"Richard Thompson" <richard.thompson@suse.com>,
"William Preston" <wpreston@suse.com>, "Yu Xu" <yu.xu@suse.com>,
netdev@vger.kernel.org, lvs-devel@vger.kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH] ipvs: Move defense_work to system_dfl_long_wq
Date: Thu, 19 Mar 2026 16:36:37 +0000 [thread overview]
Message-ID: <20260319163637.GK1753385@horms.kernel.org> (raw)
In-Reply-To: <20260317140100.24993-2-iluceno@suse.de>
On Tue, Mar 17, 2026 at 03:00:59PM +0100, Ismael Luceno wrote:
> Under synflood conditions binding defense_work to system_long_wq may
> pin it to a saturated CPU.
>
> We've observed improved throughtput on a DPDK/VPP application with
> this change. We attribute this to the reduced context switching.
>
> The defense_work handler has no per-CPU data dependencies and no cache
> locality requirements that would justify this.
>
> Signed-off-by: Ismael Luceno <iluceno@suse.de>
> ---
> Depends-on: wq/for-7.1 c116737e972e ("workqueue: Add system_dfl_long_wq for long unbound works")
Hi Ismael,
This patch seems suitable to be targeted at the nf-next tree.
That should be annotated like this:
Subject [PATCH nf-next] ipvs: ...
And the patch must compile when applied to it's target tree.
So you'll need to repost this patch once the dependency above
has reached that tree.
prev parent reply other threads:[~2026-03-19 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 14:00 [PATCH] ipvs: Move defense_work to system_dfl_long_wq Ismael Luceno
2026-03-19 16:36 ` 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=20260319163637.GK1753385@horms.kernel.org \
--to=horms@kernel.org \
--cc=andreas.taschner@suse.com \
--cc=brad.bendily@suse.com \
--cc=brendon.caligari@suse.com \
--cc=cfamullaconrad@suse.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=federico.pinca@suse.com \
--cc=firo.yang@suse.com \
--cc=fw@strlen.de \
--cc=gabriel.bertazi@suse.com \
--cc=hvdheuvel@suse.com \
--cc=iluceno@suse.de \
--cc=ja@ssi.bg \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=mkoutny@suse.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=pmladek@suse.com \
--cc=ptesarik@suse.com \
--cc=richard.thompson@suse.com \
--cc=wpreston@suse.com \
--cc=yu.xu@suse.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