From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [PATCH 1/1] ethdev: add IPv6 FL and TC field identifiers
Date: Tue, 6 Feb 2024 16:26:58 +0200 [thread overview]
Message-ID: <20240206142658.1498907-2-michaelba@nvidia.com> (raw)
In-Reply-To: <20240206142658.1498907-1-michaelba@nvidia.com>
Add new "rte_flow_field_id" enumeration values to describe both IPv6
traffic class and IPv6 flow label fields.
The TC value is "RTE_FLOW_FIELD_IPV6_TRAFFIC_CLASS" in flow API and
"ipv6_traffic_class" in testpmd command.
The FL value is "RTE_FLOW_FIELD_IPV6_FLOW_LABEL" in flow API and
"ipv6_flow_label" in testpmd command.
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
app/test-pmd/cmdline_flow.c | 1 +
doc/guides/rel_notes/release_24_03.rst | 2 ++
lib/ethdev/rte_flow.h | 4 +++-
3 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/app/test-pmd/cmdline_flow.c b/app/test-pmd/cmdline_flow.c
index 9e1048f945..a6ae4c0d29 100644
--- a/app/test-pmd/cmdline_flow.c
+++ b/app/test-pmd/cmdline_flow.c
@@ -964,6 +964,7 @@ static const char *const modify_field_ids[] = {
"random",
"ipv4_proto",
"esp_spi", "esp_seq_num", "esp_proto",
+ "ipv6_flow_label", "ipv6_traffic_class",
NULL
};
diff --git a/doc/guides/rel_notes/release_24_03.rst b/doc/guides/rel_notes/release_24_03.rst
index f08bf09e7f..10268b7879 100644
--- a/doc/guides/rel_notes/release_24_03.rst
+++ b/doc/guides/rel_notes/release_24_03.rst
@@ -68,6 +68,8 @@ New Features
* 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.
+ * Added ``RTE_FLOW_FIELD_IPV6_FLOW_LABEL`` to represent it in field ID struct.
+ * Added ``RTE_FLOW_FIELD_IPV6_TRAFFIC_CLASS`` 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 6efba67f12..e66c247e7f 100644
--- a/lib/ethdev/rte_flow.h
+++ b/lib/ethdev/rte_flow.h
@@ -3937,7 +3937,9 @@ enum rte_flow_field_id {
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. */
+ RTE_FLOW_FIELD_ESP_PROTO, /**< ESP next protocol value. */
+ RTE_FLOW_FIELD_IPV6_FLOW_LABEL, /**< IPv6 flow label. */
+ RTE_FLOW_FIELD_IPV6_TRAFFIC_CLASS/**< IPv6 traffic class. */
};
/**
--
2.25.1
next prev parent reply other threads:[~2024-02-06 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:26 [PATCH 0/1] ethdev: add IPv6 " Michael Baum
2024-02-06 14:26 ` Michael Baum [this message]
2024-02-07 13:47 ` [PATCH 1/1] ethdev: add IPv6 FL and TC " Dariusz Sosnowski
2024-02-07 15:51 ` [PATCH v2 0/1] ethdev: add IPv6 " Michael Baum
2024-02-07 15:51 ` [PATCH v2 1/1] ethdev: add IPv6 FL and TC " Michael Baum
2024-02-08 22:37 ` Ferruh Yigit
2024-02-11 8:05 ` Michael Baum
2024-02-12 17:22 ` Ferruh Yigit
2024-02-12 17:23 ` Ferruh Yigit
2024-02-14 4:08 ` 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=20240206142658.1498907-2-michaelba@nvidia.com \
--to=michaelba@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
/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).