patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Bing Zhao <bingz@nvidia.com>
To: Suanming Mou <suanmingm@nvidia.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Slava Ovsiienko <viacheslavo@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, 12 Nov 2024 07:13:16 +0000	[thread overview]
Message-ID: <PH7PR12MB6905C927EB7A6E65E4854FEFD0592@PH7PR12MB6905.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20241106093415.1062069-1-suanmingm@nvidia.com>

Thanks.

> -----Original Message-----
> From: Suanming Mou <suanmingm@nvidia.com>
> Sent: Wednesday, November 6, 2024 5:34 PM
> To: 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; 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>

Acked-by: Bing Zhao <bingz@nvidia.com>

> ---
> 
> v2: Add `repr_matching_en`` enabled by default explanation.
> 
> ---
>  doc/guides/nics/mlx5.rst | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index
> 7ced6ca8f9..64933a0823 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -460,6 +460,11 @@ Limitations
>    - The field type ``RTE_FLOW_FIELD_VALUE`` must be the base (``b``)
> field.
>    - The field type ``RTE_FLOW_FIELD_RANDOM`` can only be compared with
>      ``RTE_FLOW_FIELD_VALUE``.
> +  - In switch mode, when ``repr_matching_en`` flag is enabled (by
> default)
> +    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.
> 
>  - No Tx metadata go to the E-Switch steering domain for the Flow group 0.
>    The flows within group 0 and set metadata action are rejected by
> hardware.
> --
> 2.34.1


  reply	other threads:[~2024-11-12  7:13 UTC|newest]

Thread overview: 7+ 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 [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=PH7PR12MB6905C927EB7A6E65E4854FEFD0592@PH7PR12MB6905.namprd12.prod.outlook.com \
    --to=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).