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>,
Alexander Kozyrev <akozyrev@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix VLAN strip info for CQE compression
Date: Tue, 24 Mar 2026 15:03:47 +0200 [thread overview]
Message-ID: <fcb9d7d4-44a3-47d3-b8c9-2ff7d3d97a25@nvidia.com> (raw)
In-Reply-To: <20260320160001.787223-1-dsosnowski@nvidia.com>
Hi,
On 20/03/2026 6:00 PM, Dariusz Sosnowski wrote:
> When L3/L4 mini CQE format is used with CQE compression
> (rxq_cqe_comp_en set to 4 in lower 3 bits),
> each mini CQE reports packet header info for relevant packet.
> One bit in that header info is dedicated to CVLAN info,
> used to determine whether CVLAN is present in the received packet.
> This info is used to determine VLAN stripping info
> when relevant offload is enabled.
>
> Before this patch, users might have seen incorrectly set/unset
> RTE_MBUF_F_RX_VLAN and RTE_MBUF_F_RX_VLAN_STRIPPED flags because:
>
> - Struct for mlx5 mini CQE incorrectly defined the location
> of packet header info byte - it was swapped with neighboring
> reserved byte.
> - CVLAN bit was checked incorrectly because of cast to uint16_t
> and big endian change. It should be checked as uint8_t.
>
> This patch addresses the above.
>
> Fixes: 54c2d46b160f ("net/mlx5: support flow tag and packet header miniCQEs")
> Cc: akozyrev@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2026-03-24 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 16:00 [PATCH] net/mlx5: fix VLAN strip info for CQE compression Dariusz Sosnowski
2026-03-24 13:03 ` 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=fcb9d7d4-44a3-47d3-b8c9-2ff7d3d97a25@nvidia.com \
--to=rasland@nvidia.com \
--cc=akozyrev@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