From: Stephen Hemminger <stephen@networkplumber.org>
To: Suanming Mou <suanmingm@nvidia.com>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Matan Azrad <matan@nvidia.com>, <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH] doc: update match with compare result item limitation
Date: Wed, 6 Nov 2024 10:29:19 -0800 [thread overview]
Message-ID: <20241106102919.0171a9cc@hermes.local> (raw)
In-Reply-To: <20241105014736.1006927-1-suanmingm@nvidia.com>
On Tue, 5 Nov 2024 09:47:36 +0800
Suanming Mou <suanmingm@nvidia.com> wrote:
> + - 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.
These sentences are hard to read, the wording is very awkward.
Have no detailed insight into the mlx5 matching but maybe this wording:
In switch mode, when the ``repr_matching_en`` flag is used then matching
with ingress comparison is not supported because an implicit rule is required
to match the REPRESENTED_PORT. And that implicit rule would conflict with the
ingress compare rule.
prev parent reply other threads:[~2024-11-06 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 1:47 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-06 18:29 ` Stephen Hemminger [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=20241106102919.0171a9cc@hermes.local \
--to=stephen@networkplumber.org \
--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).