From: Kevin Traynor <ktraynor@redhat.com>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, stable@dpdk.org
Cc: bluca@debian.org, xuemingl@nvidia.com,
Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: Re: [PATCH 22.11] net/mlx5: fix control flow leakage for external SQ
Date: Fri, 21 Nov 2025 14:16:28 +0000 [thread overview]
Message-ID: <5e81447a-0edc-4ec7-893b-39de52dc3ccc@redhat.com> (raw)
In-Reply-To: <20251118165158.1315992-1-viacheslavo@nvidia.com>
On 18/11/2025 16:51, Viacheslav Ovsiienko wrote:
> [ upstream commit 3bf9f0f9f0beb8dcd4f3b316c3216a87bc9ab49f ]
>
> There is the private API rte_pmd_mlx5_external_sq_enable(),
> that allows application to create the Send Queue (SQ) on its own
> and then enable this queue usage as "external SQ".
>
> On this enabling call some implicit flows are created to provide
> compliant SQs behavior - copy metadata register, forward queue
> originated packet to correct VF, etc.
>
> These implicit flows are marked as "external" ones, and there is
> no cleanup on device start and stop for this kind of flows.
> Also, PMD has no knowledge if external SQ is still in use by
> application and implicit cleanup can not be performed.
>
> As a result, on multiple device start/stop cycles application
> re-creates and re-enables many external SQs, causing implicit
> flow tables overflow.
>
> To resolve this issue the rte_pmd_mlx5_external_sq_disable()
> API is provided, that allows to application to notify PMD
> the external SQ is not in usage anymore and related implicit
> flows can be dismissed.
>
> Fixes: 26e1eaf2dac4 ("net/mlx5: support device control for E-Switch default rule")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_flow.h | 12 ++--
> drivers/net/mlx5/mlx5_flow_hw.c | 106 +++++++++++++++++++++++++++++++-
> drivers/net/mlx5/mlx5_trigger.c | 2 +-
> drivers/net/mlx5/mlx5_txq.c | 54 ++++++++++++++--
> drivers/net/mlx5/rte_pmd_mlx5.h | 18 ++++++
> drivers/net/mlx5/version.map | 1 +
> 6 files changed, 181 insertions(+), 12 deletions(-)
>
Hi Slava,
I applied this to 24.11 branch with a small rebase, but it's causing
build errors, so I think it will need a dedicated 24.11 backport.
thanks,
Kevin.
prev parent reply other threads:[~2025-11-21 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 16:51 Viacheslav Ovsiienko
2025-11-21 14:16 ` Kevin Traynor [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=5e81447a-0edc-4ec7-893b-39de52dc3ccc@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=dsosnowski@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.com \
--cc=xuemingl@nvidia.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;
as well as URLs for NNTP newsgroup(s).