DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: "Jiawei(Jonny) Wang" <jiaweiw@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH 1/2] net/mlx5: fix metadata and meter split shared tag
Date: Sun, 21 Nov 2021 14:38:59 +0000	[thread overview]
Message-ID: <DM4PR12MB5312BCF3761096B0CBF1F970CF9E9@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211119130201.14217-1-jiaweiw@nvidia.com>

Hi,

> -----Original Message-----
> From: Jiawei(Jonny) Wang <jiaweiw@nvidia.com>
> Sent: Friday, November 19, 2021 3:02 PM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> stable@dpdk.org
> Subject: [PATCH 1/2] net/mlx5: fix metadata and meter split shared tag
> 
> In the metadata flow split, PMD created the prefix subflow
> with removed Queue or RSS action and appended the set tag and
> copy table jump actions. If the flow being split for metadata
> was the meter prefix subflow, the driver supposed to share the same
> meter split tag action for the metadata split flow. There was the wrong
> check for preceding meter split tag action, causing append with metadata
> split set tag action and resulting the meter suffix subflow was missed
> due to tag value mismatch.
> 
> This patch adds the checking before copying into extend action list,
> to make sure the correct shared tag is used.
> 
> Fixes: 8d72fa668964 ("net/mlx5: share tag between meter and metadata")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2021-11-21 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 13:02 Jiawei Wang
2021-11-19 13:02 ` [PATCH 2/2] net/mlx5: fix the mismatch metadata flow with meter action Jiawei Wang
2021-11-21 14:38 ` 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=DM4PR12MB5312BCF3761096B0CBF1F970CF9E9@DM4PR12MB5312.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --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).