From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: <dev@dpdk.org>
Cc: <xuemingl@nvidia.com>, <rasland@nvidia.com>, <matan@nvidia.com>,
<stable@dpdk.org>
Subject: [PATCH] doc: fix modify field action description for mlx5
Date: Thu, 24 Feb 2022 17:57:37 +0200 [thread overview]
Message-ID: <20220224155737.18039-1-viacheslavo@nvidia.com> (raw)
This patch adds mlx5 specifics description about
handling the Ethernet type by modify field action
for VLAN-ed traffic.
Fixes: 641dbe4fb053 ("net/mlx5: support modify field flow action")
Cc: stable@dpdk.org
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
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 7b04e9bac5..efc971a89e 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -407,6 +407,11 @@ Limitations
- Modification of the 802.1Q Tag, VXLAN Network or GENEVE Network ID's is not supported.
- Encapsulation levels are not supported, can modify outermost header fields only.
- Offsets must be 32-bits aligned, cannot skip past the boundary of a field.
+ - if the field type is RTE_FLOW_FIELD_MAC_TYPE and packet contains one
+ or more VLAN headers, the meaningful type field following the the last
+ VLAN header is used as modify field operation argument. The modify field
+ action is not intended to modify VLAN headers type field, dedicated VLAN
+ push and pop actions should be used instead.
- IPv6 header item 'proto' field, indicating the next header protocol, should
not be set as extension header.
--
2.18.1
next reply other threads:[~2022-02-24 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 15:57 Viacheslav Ovsiienko [this message]
2022-02-24 16:01 ` [PATCH v2] " Viacheslav Ovsiienko
2022-03-10 9:23 ` Raslan Darawsheh
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=20220224155737.18039-1-viacheslavo@nvidia.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=xuemingl@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).