From: Raslan Darawsheh <rasland@nvidia.com>
To: Suanming Mou <suanmingm@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2] doc: update match with compare result item limitation
Date: Tue, 26 Nov 2024 08:10:19 +0000 [thread overview]
Message-ID: <CH3PR12MB8460CD2B7DC9DD1B9F8EC3B0CF2F2@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20241106093415.1062069-1-suanmingm@nvidia.com>
Hi,
From: Suanming Mou <suanmingm@nvidia.com>
Sent: Wednesday, November 6, 2024 11:34 AM
To: Dariusz Sosnowski; Slava Ovsiienko; Bing Zhao; Ori Kam; Matan Azrad
Cc: dev@dpdk.org; stable@dpdk.org
Subject: [PATCH v2] doc: update match with compare result item limitation
In switch mode, when ``repr_matching_en`` flag is enabled in the devarg,
the match with compare result item is not supported to the ``ingress``
rule as an implicit REPRESENTED_PORT need to be added to the matcher.
That REPRESENTED_PORT item conflicts with the single item limitation for
match with compare result item.
Fixes: cb25df7ce9d6 ("net/mlx5: support comparison matching")
Cc: stable@dpdk.org
Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
---
v2: Add `repr_matching_en`` enabled by default explanation.
----
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2024-11-26 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 1:47 [PATCH] " Suanming Mou
2024-11-05 3:48 ` Bing Zhao
2024-11-06 9:01 ` Suanming Mou
2024-11-06 9:34 ` [PATCH v2] " Suanming Mou
2024-11-12 7:13 ` Bing Zhao
2024-11-26 8:10 ` Raslan Darawsheh [this message]
2024-11-06 18:29 ` [PATCH] " Stephen Hemminger
2024-11-11 8:15 ` Bing Zhao
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=CH3PR12MB8460CD2B7DC9DD1B9F8EC3B0CF2F2@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=rasland@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;
as well as URLs for NNTP newsgroup(s).