From: Ori Kam <orika@nvidia.com>
To: <thomas@monjalon.net>, <andrew.rybchenko@oktetlabs.ru>,
Ray Kinsella <mdr@ashroe.eu>
Cc: <orika@nvidia.com>, <dev@dpdk.org>, <ajit.khaparde@broadcom.com>,
<viacheslavo@nvidia.com>, <ferruh.yigit@intel.com>,
<matan@nvidia.com>, <rasland@nvidia.com>, <gakhil@marvell.com>
Subject: [dpdk-dev] [PATCH v2 1/2] ethdev: announce change to action modify data
Date: Tue, 3 Aug 2021 11:57:53 +0300 [thread overview]
Message-ID: <20210803085754.643180-1-orika@nvidia.com> (raw)
In-Reply-To: <20210802141004.353754-1-matan@nvidia.com>
In the current implementation,
the action rte_flow_action_modify_field is not well defined
for fields larger than 64 bits (for example IPv6 source)
In addition, the byte order is also not well defined.
Both of those issue should be fixed.
Signed-off-by: Ori Kam <orika@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
---
V2:
Fix typo.
---
doc/guides/rel_notes/deprecation.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d9c0e65921..b530616281 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -158,3 +158,7 @@ Deprecation Notices
* security: The functions ``rte_security_set_pkt_metadata`` and
``rte_security_get_userdata`` will be made inline functions and additional
flags will be added in structure ``rte_security_ctx`` in DPDK 21.11.
+
+* ethdev: The struct ``rte_flow_action_modify_data`` will be modified
+ to support modifying larger fields than 64 bits.
+ In addition, documentation will be updated to clarify byte order.
--
2.25.1
next prev parent reply other threads:[~2021-08-03 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 14:10 [dpdk-dev] [PATCH " Matan Azrad
2021-08-02 14:10 ` [dpdk-dev] [PATCH 2/2] ethdev: announce moving to general modify function Matan Azrad
2021-08-03 8:57 ` Ori Kam [this message]
2021-08-03 8:57 ` [dpdk-dev] [PATCH v2 " Ori Kam
2021-08-03 18:05 ` Ajit Khaparde
2021-08-07 13:33 ` Jerin Jacob
2021-08-07 19:34 ` Thomas Monjalon
2021-08-03 18:10 ` [dpdk-dev] [PATCH v2 1/2] ethdev: announce change to action modify data Ajit Khaparde
2021-08-04 12:10 ` Andrew Rybchenko
2021-08-07 13:33 ` Jerin Jacob
2021-08-07 19:26 ` Thomas Monjalon
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=20210803085754.643180-1-orika@nvidia.com \
--to=orika@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gakhil@marvell.com \
--cc=matan@nvidia.com \
--cc=mdr@ashroe.eu \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--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).