From: Salem Sol <salems@nvidia.com>
To: dev@dpdk.org
Cc: Salem Sol <salems@nvidia.com>, Ori Kam <orika@nvidia.com>,
Xiaoyun Li <xiaoyun.li@intel.com>
Subject: [dpdk-dev] [PATCH v2 4/7] app/testpmd: support VXLAN encap for sample action
Date: Tue, 16 Mar 2021 10:08:28 +0200 [thread overview]
Message-ID: <20210316080832.22541-5-salems@nvidia.com> (raw)
In-Reply-To: <20210316080832.22541-1-salems@nvidia.com>
Add support for rte_flow_action_vxlan_encap as a sample action.
The example of test-pmd command:
1. set vxlan ip-version ... vni ... udp-src ...
set raw_encap 1 eth src.../ ipv4.../...
set sample_actions 2 vxlan_encap / port_id id 0 / end
flow create 0 ... pattern eth / end actions
sample ratio 1 index 2 / raw_encap index 1 / port_id id 0...
The flow will result in all the matched egress packets will be
encapsulated and sent to wire, and also mirrored the packets
using VXLAN encapsulation data and sent to wire.
Signed-off-by: Salem Sol <salems@nvidia.com>
---
app/test-pmd/cmdline_flow.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/app/test-pmd/cmdline_flow.c b/app/test-pmd/cmdline_flow.c
index 84676a2e45..61dfaab8fd 100644
--- a/app/test-pmd/cmdline_flow.c
+++ b/app/test-pmd/cmdline_flow.c
@@ -582,6 +582,7 @@ struct rte_flow_action_queue sample_queue[RAW_SAMPLE_CONFS_MAX_NUM];
struct rte_flow_action_count sample_count[RAW_SAMPLE_CONFS_MAX_NUM];
struct rte_flow_action_port_id sample_port_id[RAW_SAMPLE_CONFS_MAX_NUM];
struct rte_flow_action_raw_encap sample_encap[RAW_SAMPLE_CONFS_MAX_NUM];
+struct action_vxlan_encap_data sample_vxlan_encap[RAW_SAMPLE_CONFS_MAX_NUM];
struct action_rss_data sample_rss_data[RAW_SAMPLE_CONFS_MAX_NUM];
struct rte_flow_action_vf sample_vf[RAW_SAMPLE_CONFS_MAX_NUM];
@@ -1615,6 +1616,7 @@ static const enum index next_action_sample[] = {
ACTION_COUNT,
ACTION_PORT_ID,
ACTION_RAW_ENCAP,
+ ACTION_VXLAN_ENCAP,
ACTION_NEXT,
ZERO,
};
@@ -7949,6 +7951,11 @@ cmd_set_raw_parsed_sample(const struct buffer *in)
(const void *)action->conf, size);
action->conf = &sample_vf[idx];
break;
+ case RTE_FLOW_ACTION_TYPE_VXLAN_ENCAP:
+ size = sizeof(struct rte_flow_action_vxlan_encap);
+ parse_setup_vxlan_encap_data(&sample_vxlan_encap[idx]);
+ action->conf = &sample_vxlan_encap[idx].conf;
+ break;
default:
printf("Error - Not supported action\n");
return;
--
2.21.0
next prev parent reply other threads:[~2021-03-16 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 8:08 [dpdk-dev] [PATCH v2 0/7] Add support for VXLAN and NVGRE encap as a sample actions Salem Sol
2021-03-16 8:08 ` [dpdk-dev] [PATCH v2 1/7] app/testpmd: store VXLAN/NVGRE encap data globally Salem Sol
2021-03-16 8:08 ` [dpdk-dev] [PATCH v2 2/7] net/mlx5: support VXLAN encap action in sample Salem Sol
2021-03-16 8:08 ` [dpdk-dev] [PATCH v2 3/7] net/mlx5: support NVGRE " Salem Sol
2021-03-16 8:08 ` Salem Sol [this message]
2021-03-16 8:08 ` [dpdk-dev] [PATCH v2 5/7] app/testpmd: support NVGRE encap for sample action Salem Sol
2021-03-16 8:08 ` [dpdk-dev] [PATCH v2 6/7] doc: update sample actions support in testpmd guide Salem Sol
2021-03-16 8:08 ` [dpdk-dev] [PATCH v2 7/7] doc: update sample actions support in mlx5 guide Salem Sol
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=20210316080832.22541-5-salems@nvidia.com \
--to=salems@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=xiaoyun.li@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).