From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, dev@dpdk.org
Cc: mkashani@nvidia.com, stable@dpdk.org,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH] net/mlx5: fix IPv6 SHR flex node header length definition
Date: Thu, 5 Feb 2026 14:01:42 +0200 [thread overview]
Message-ID: <11b98129-abe8-4fe6-ab0a-a227b007c312@nvidia.com> (raw)
In-Reply-To: <20251225110201.590263-1-getelson@nvidia.com>
Hi,
On 25/12/2025 1:02 PM, Gregory Etelson wrote:
> MLX5 PARSE_GRAPH_NODE defines the header_length_field_offset_mode bit,
> starting from ConnectX-8. The bit value must match
> HCA_CAP.header_length_field_offset_mode.
>
> 1. The patch copies header_length_field_offset_mode bit from a port
> PARSE_GRAPH node capabilities to PARSE_GRAPH node definition.
>
> 2. The patch fixes the header_length_field_offset value to match
> HCA_CAP.header_length_mask_width.
>
> 3. The patch replaces the static value in PARSE_GRAPH node
> header_length_field_mask definition with one that matches
> HCA_CAP.header_length_mask_width.
>
> Fixes: a2234609bf7e ("net/mlx5: fix flex flow item header length")
> Cc: stable@dpdk.org
>
> Signed-off-by: Gregory Etelson <getelson@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-02-05 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 11:02 [PATCH] net/mlx5: fix IPv6 SHR flex node header length definition Gregory Etelson
2026-02-05 12:01 ` 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=11b98129-abe8-4fe6-ab0a-a227b007c312@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@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