From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: <dev@dpdk.org>
Cc: <matan@nvidia.com>, <rasland@nvidia.com>, <orika@nvidia.com>,
<dsosnowski@nvidia.com>
Subject: [PATCH v2 4/6] ethdev: add modify action support for IPsec fields
Date: Wed, 7 Feb 2024 14:13:52 +0200 [thread overview]
Message-ID: <20240207121354.27175-4-viacheslavo@nvidia.com> (raw)
In-Reply-To: <20240207121354.27175-1-viacheslavo@nvidia.com>
The following IPsec related field definitions added:
- RTE_FLOW_FIELD_ESP_SPI - SPI value in IPsec header
- RTE_FLOW_FIELD_ESP_SEQ_NUM - sequence number in header
- RTE_FLOW_FIELD_ESP_PROTO - next protocol value in trailer
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
doc/guides/rel_notes/release_24_03.rst | 3 +++
lib/ethdev/rte_flow.h | 5 ++++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/doc/guides/rel_notes/release_24_03.rst b/doc/guides/rel_notes/release_24_03.rst
index 140f7b0ac5..0403157202 100644
--- a/doc/guides/rel_notes/release_24_03.rst
+++ b/doc/guides/rel_notes/release_24_03.rst
@@ -68,6 +68,9 @@ New Features
* **Added new field IDs in the experimental ``enum rte_flow_field_id``:
* Added ``RTE_FLOW_FIELD_IPV4_PROTO`` to represent it in field ID struct.
+ * Added ``RTE_FLOW_FIELD_ESP_SPI`` to represent it in field ID struct.
+ * Added ``RTE_FLOW_FIELD_ESP_SEQ_NUM`` to represent it in field ID struct.
+ * Added ``RTE_FLOW_FIELD_ESP_PROTO`` to represent it in field ID struct.
* ** Support for getting the number of used descriptors of a Tx queue. **
diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h
index 84af730dc7..6efba67f12 100644
--- a/lib/ethdev/rte_flow.h
+++ b/lib/ethdev/rte_flow.h
@@ -3934,7 +3934,10 @@ enum rte_flow_field_id {
RTE_FLOW_FIELD_IPV4_TOTAL_LEN, /**< IPv4 total length. */
RTE_FLOW_FIELD_IPV6_PAYLOAD_LEN,/**< IPv6 payload length. */
RTE_FLOW_FIELD_RANDOM, /**< Random value. */
- RTE_FLOW_FIELD_IPV4_PROTO /**< IPv4 next protocol. */
+ RTE_FLOW_FIELD_IPV4_PROTO, /**< IPv4 next protocol. */
+ RTE_FLOW_FIELD_ESP_SPI, /**< ESP SPI. */
+ RTE_FLOW_FIELD_ESP_SEQ_NUM, /**< ESP Sequence Number. */
+ RTE_FLOW_FIELD_ESP_PROTO /**< ESP next protocol value. */
};
/**
--
2.18.1
next prev parent reply other threads:[~2024-02-07 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 12:13 [PATCH v2 1/6] ethdev: add modify IPv4 next protocol field Viacheslav Ovsiienko
2024-02-07 12:13 ` [PATCH v2 2/6] app/testpmd: add modify IPv4 next protocol command line Viacheslav Ovsiienko
2024-02-07 12:13 ` [PATCH v2 3/6] net/mlx5: add modify IPv4 protocol implementation Viacheslav Ovsiienko
2024-02-07 12:13 ` Viacheslav Ovsiienko [this message]
2024-02-07 12:13 ` [PATCH v2 5/6] app/testpmd: add modify ESP related fields command line Viacheslav Ovsiienko
2024-02-07 12:13 ` [PATCH v2 6/6] net/mlx5: add modify field action IPsec support Viacheslav Ovsiienko
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=20240207121354.27175-4-viacheslavo@nvidia.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@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).