patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ori Kam <orika@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v1 1/2] net/mlx5: disallow duplicated tag index in pattern template
Date: Wed, 17 May 2023 17:11:14 +0000	[thread overview]
Message-ID: <MW2PR12MB466689FABC3F8F9AA4F949D5D67E9@MW2PR12MB4666.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230516054329.1397016-2-rongweil@nvidia.com>

Hi Rongwei,

> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Tuesday, May 16, 2023 8:43 AM
> 
> Duplicated tag index in pattern template will most likely cause
> matching failures such as "template tag index is 0 data mask 0xff /
> tag index is 0 data mask 0xffff / end"
> 
> If the upper layer application needs to match the same tag twice
> with different masks, it should be consolidated into one rte_item
> with the desired mask.
> 
> "template tag index is 0 data mask 0xff / tag index is 0 data mask
> 0xff00 / end" should be present as "template tag index is 0 data mask
> 0xffff / end"
> 
> Cc: stable@dpdk.org
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---

Acked-by: Ori Kam <orika@nvidia.com>

  reply	other threads:[~2023-05-17 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230516054329.1397016-1-rongweil@nvidia.com>
2023-05-16  5:43 ` Rongwei Liu
2023-05-17 17:11   ` Ori Kam [this message]
2023-05-16  5:43 ` [PATCH v1 2/2] net/mlx5: fix sws duplicated tag index matching Rongwei Liu

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=MW2PR12MB466689FABC3F8F9AA4F949D5D67E9@MW2PR12MB4666.namprd12.prod.outlook.com \
    --to=orika@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rongweil@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).