From: Suanming Mou <suanmingm@nvidia.com>
To: <ferruh.yigit@amd.com>, Aman Singh <aman.deep.singh@intel.com>,
"Yuying Zhang" <yuying.zhang@intel.com>
Cc: <dev@dpdk.org>
Subject: [PATCH v3 1/2] doc: add modify_field action description
Date: Wed, 11 Oct 2023 19:30:55 +0800 [thread overview]
Message-ID: <20231011113057.454215-1-suanmingm@nvidia.com> (raw)
In-Reply-To: <20230808083741.8193-1-suanmingm@nvidia.com>
This commit adds the missing modify_field action description to
`testpmd_funcs.rst`.
Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
---
v3: add modify_field description.
---
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 67968ecb7f..04c502798a 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -4108,6 +4108,27 @@ This section lists supported actions and their attributes, if any.
- ``mtr_init_color {value}``: initial color value (green/yellow/red)
- ``mtr_state {unsigned}``: meter state (disabled/enabled)
+- ``modify_field``: Modify packet field
+
+ - ``op``: modify operation (set/add/sub)
+ - ``dst_type``: the destination field to be modified, the supported fields as
+ ``enum rte_flow_field_id`` listed.
+ - ``dst_level``: destination field level.
+ - ``dst_tag_index``: destination field tag array.
+ - ``dst_type_id``: destination field type ID.
+ - ``dst_class``: destination field class ID.
+ - ``dst_offset``: destination field bit offset.
+ - ``src_type``: the modify source field, the supported fields as
+ ``enum rte_flow_field_id`` listed.
+ - ``src_level``: source field level.
+ - ``src_tag_index``: source field tag array.
+ - ``src_type_id``: source field type ID.
+ - ``src_class``: source field class ID.
+ - ``src_offset``: source field bit offset.
+ - ``src_value``: source immediate value.
+ - ``src_ptr``: pointer to source immediate value.
+ - ``width``: number of bits to copy.
+
Destroying flow rules
~~~~~~~~~~~~~~~~~~~~~
--
2.34.1
next prev parent reply other threads:[~2023-10-11 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 8:37 [PATCH] ethdev: add TCP/IP modify field IDs Suanming Mou
2023-09-08 3:49 ` [PATCH v2] " Suanming Mou
2023-10-10 10:24 ` Ferruh Yigit
2023-10-11 0:11 ` Suanming Mou
2023-10-11 8:58 ` Suanming Mou
2023-10-11 11:30 ` Suanming Mou [this message]
2023-10-11 11:30 ` [PATCH v3 2/2] " Suanming Mou
2023-10-12 14:17 ` [PATCH v3 1/2] doc: add modify_field action description Ferruh Yigit
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=20231011113057.454215-1-suanmingm@nvidia.com \
--to=suanmingm@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=yuying.zhang@intel.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).