From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix flow mark reading after reconfigure
Date: Tue, 24 Feb 2026 13:40:00 +0200 [thread overview]
Message-ID: <6017e0cc-e97f-4dda-ae31-6c249ba1e052@nvidia.com> (raw)
In-Reply-To: <20260211081239.191118-1-dsosnowski@nvidia.com>
Hi,
On 11/02/2026 10:12 AM, Dariusz Sosnowski wrote:
> mlx5 PMD supports flow mark action which attaches additional
> metadata to received packets. This metadata is stored
> in the rte_mbuf in hash.fdir.hi field and applications
> are notified about it with RTE_MBUF_F_RX_FDIR mbuf flag.
>
> When working with HW Steering flow engine,
> mlx5 PMD reads the HW completion entry field with flow mark value
> if and only if at least one template table with flow mark action
> was created.
> Whenever table was created mlx5 PMD updated the private
> data of each Rx queue to inform
> Rx burst function to read HW field.
>
> Whenever application reconfigures any of the Rx queues
> through additional call to rte_eth_rx_queue_setup(),
> this private Rx queue data is reset, but information
> about existence of flow mark was not restored by PMD.
> As a result, reconfiguration caused applications
> to not receive flow mark metadata.
>
> This patch fixes that behavior. Whenever port is started,
> PMD will check if flow mark action is used and update
> relevant private Rx queue data struct.
>
> Fixes: 1deadfd709f5 ("net/mlx5: add HW mark action")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2026-02-24 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 8:12 [PATCH] net/mlx5: fix flow mark reading after reconfigure Dariusz Sosnowski
2026-02-24 11:40 ` Raslan Darawsheh [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=6017e0cc-e97f-4dda-ae31-6c249ba1e052@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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