From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lijuan.tu@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V4 01/13] conf/vf_l3fwd_base: add more flows
Date: Tue, 30 Mar 2021 15:05:13 +0800 [thread overview]
Message-ID: <20210330070525.5056-2-yufengx.mo@intel.com> (raw)
In-Reply-To: <20210330070525.5056-1-yufengx.mo@intel.com>
add vf_l3fwd_base more flows configuration.
Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
conf/vf_l3fwd_base.cfg | 93 +++++++++++++++++++++++++++++++++++++++++-
1 file changed, 92 insertions(+), 1 deletion(-)
diff --git a/conf/vf_l3fwd_base.cfg b/conf/vf_l3fwd_base.cfg
index 9d9ede33..8d281144 100644
--- a/conf/vf_l3fwd_base.cfg
+++ b/conf/vf_l3fwd_base.cfg
@@ -1,6 +1,50 @@
+# stream_type= "tcp"/"udp"/"raw". If not set this key, default is "raw"
+#
[suite]
l3fwd_flows = {
"ipv4": {
+ "em": [
+ {
+ "ipv4": {
+ "dst": "101.0.0.0",
+ "src": "100.10.0.1"
+ },
+ "udp": {
+ "dst": 11,
+ "src": 101
+ }
+ },
+ {
+ "ipv4": {
+ "dst": "201.0.0.0",
+ "src": "200.20.0.1"
+ },
+ "udp": {
+ "dst": 12,
+ "src": 102
+ }
+ },
+ {
+ "ipv4": {
+ "dst": "111.0.0.0",
+ "src": "100.30.0.1"
+ },
+ "udp": {
+ "dst": 11,
+ "src": 101
+ }
+ },
+ {
+ "ipv4": {
+ "dst": "211.0.0.0",
+ "src": "200.40.0.1"
+ },
+ "udp": {
+ "dst": 11,
+ "src": 102
+ }
+ }
+ ],
"lpm": [
"198.18.0.0/24",
"198.18.1.0/24",
@@ -11,4 +55,51 @@ l3fwd_flows = {
"198.18.6.0/24",
"198.18.7.0/24"
]
- }, }
\ No newline at end of file
+ },
+ "ipv6": {
+ "em": [
+ {
+ "ipv6": {
+ "dst": "fe80:0000:0000:0000:021e:67ff:fe00:0000",
+ "src": "fe80:0000:0000:0000:021b:21ff:fe91:3805"
+ },
+ "udp": {
+ "dst": 101,
+ "src": 11 }
+ },
+ {
+ "ipv6": {
+ "dst": "fe90:0000:0000:0000:021e:67ff:fe00:0000",
+ "src": "fe90:0000:0000:0000:021b:21ff:fe91:3805" },
+ "udp": {
+ "dst": 102,
+ "src": 12 }
+ },
+ {
+ "ipv6": {
+ "dst": "fea0:0000:0000:0000:021e:67ff:fe00:0000",
+ "src": "fea0:0000:0000:0000:021b:21ff:fe91:3805" },
+ "udp": {
+ "dst": 101,
+ "src": 11 }
+ },
+ {
+ "ipv6": {
+ "dst": "feb0:0000:0000:0000:021e:67ff:fe00:0000",
+ "src": "feb0:0000:0000:0000:021b:21ff:fe91:3805" },
+ "udp": {
+ "dst": 102,
+ "src": 12 }
+ }
+ ],
+ "lpm": [
+ "3201:20:00:00:00:00:00:00/48",
+ "3201:20:00:00:01:00:00:00/48",
+ "3201:20:00:00:02:00:00:00/48",
+ "3201:20:00:00:03:00:00:00/48",
+ "3201:20:00:00:04:00:00:00/48",
+ "3201:20:00:00:05:00:00:00/48",
+ "3201:20:00:00:06:00:00:00/48",
+ "3201:20:00:00:07:00:00:00/48"
+ ]
+ } }
--
2.21.0
next prev parent reply other threads:[~2021-03-30 7:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 7:05 [dts] [PATCH V4 00/13] vf_l3fwd_kernelpf: add more test scenario yufengmx
2021-03-30 7:05 ` yufengmx [this message]
2021-03-30 7:05 ` [dts] [PATCH V4 02/13] tests/perf_test_base: extend vf l3fwd content yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 03/13] conf/vf_l3fwd_em_kernelpf: configuration yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 04/13] tests/vf_l3fwd_em_kernelpf: script yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 05/13] conf/vf_l3fwd_kernelpf: configuration yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 06/13] tests/vf_l3fwd_kernelpf: add more test scenario yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 07/13] conf/vf_l3fwd_lpm_ipv4_kernelpf: configuration yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 08/13] tests/vf_l3fwd_lpm_ipv4_kernelpf: script yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 09/13] conf/vf_l3fwd_lpm_ipv4_rfc2544_kernelpf: configuration yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 10/13] tests/vf_l3fwd_lpm_ipv4_rfc2544_kernelpf: script yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 11/13] conf/vf_l3fwd_lpm_ipv6_kernelpf: configuration yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 12/13] tests/vf_l3fwd_lpm_ipv6_kernelpf: script yufengmx
2021-03-30 7:05 ` [dts] [PATCH V4 13/13] tests/perf_test_base: script yufengmx
2021-03-31 5:54 ` [dts] [PATCH V4 00/13] vf_l3fwd_kernelpf: add more test scenario Tu, Lijuan
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=20210330070525.5056-2-yufengx.mo@intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@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).