patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Gavin Li <gavinl@nvidia.com>,
	dev@dpdk.org, dsosnowski@nvidia.com, viacheslavo@nvidia.com,
	orika@nvidia.com, suanmingm@nvidia.com, matan@nvidia.com
Cc: jiaweiw@nvidia.com, stable@dpdk.org, Bing Zhao <bingz@nvidia.com>
Subject: Re: [PATCH V3] net/mlx5: fix IPv6 DSCP offset in HWS sync API
Date: Sun, 16 Nov 2025 17:34:11 +0200	[thread overview]
Message-ID: <8719bca4-d4be-4b5b-8083-6fb34b7de6d1@nvidia.com> (raw)
In-Reply-To: <20251112134236.195614-1-gavinl@nvidia.com>

Hi,

On 12/11/2025 3:42 PM, Gavin Li wrote:
> The processing of field IPv6 DSCP via the synchronous flow API is
> different between software and hardware steering engines(HWS). The bit
> shift handling for IPv6 DSCP was not handled in HWS, resulting in
> incorrect data in the field.
> 
> To resolve this, bit shift handling should be added to HWS.
> 
> Fixes: ec1e7a5ceb69 ("net/mlx5: update IPv6 traffic class modification")
> Cc: stable@dpdk.org
> Signed-off-by: Gavin Li <gavinl@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh


      reply	other threads:[~2025-11-16 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  7:28 [PATCH] net/mlx5: fix IPv6 DSCP offset in NT HWS API Gavin Li
2025-11-12  8:58 ` Bing Zhao
2025-11-12  9:09   ` Thomas Monjalon
2025-11-12 12:47     ` Minggang(Gavin) Li
2025-11-12 13:01 ` [PATCH V2] net/mlx5: fix IPv6 DSCP offset in HWS sync API Gavin Li
2025-11-12 13:42   ` [PATCH V3] " Gavin Li
2025-11-16 15:34     ` 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=8719bca4-d4be-4b5b-8083-6fb34b7de6d1@nvidia.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=gavinl@nvidia.com \
    --cc=jiaweiw@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;
as well as URLs for NNTP newsgroup(s).