From: Xie wei <weix.xie@intel.com>
To: dts@dpdk.org
Cc: Xie wei <weix.xie@intel.com>
Subject: [dts] [dts 6/7] test_plans/ipfrag_test_plan:update test plan to sync with testsuite
Date: Thu, 3 Sep 2020 17:57:45 +0800 [thread overview]
Message-ID: <20200903095746.32389-7-weix.xie@intel.com> (raw)
In-Reply-To: <20200903095746.32389-1-weix.xie@intel.com>
Signed-off-by: Xie wei <weix.xie@intel.com>
---
test_plans/ipfrag_test_plan.rst | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/test_plans/ipfrag_test_plan.rst b/test_plans/ipfrag_test_plan.rst
index 9c0afed..31dcc7b 100644
--- a/test_plans/ipfrag_test_plan.rst
+++ b/test_plans/ipfrag_test_plan.rst
@@ -133,6 +133,34 @@ Prerequisites
- The set of logical cores to execute the packet forwarding task
- Mapping of the NIC RX queues to logical cores handling them.
+6. Set lpm table for IPv4 & IPv6 packet::
+
+ sed -i '/l3fwd_ipv4_route_array\[\].*{/,/^\}\;/c\\static struct l3fwd_ipv4_route l3fwd_ipv4_route_array[] = {\
+ {RTE_IPV4(100,10,0,0), 16, 1},\
+ {RTE_IPV4(100,20,0,0), 16, 1},\
+ {RTE_IPV4(100,30,0,0), 16, 0},\
+ {RTE_IPV4(100,40,0,0), 16, 0},\
+ {RTE_IPV4(100,50,0,0), 16, 1},\
+ {RTE_IPV4(100,60,0,0), 16, 1},\
+ {RTE_IPV4(100,70,0,0), 16, 0},\
+ {RTE_IPV4(100,80,0,0), 16, 0},\
+ };' examples/ip_fragmentation/main.c
+
+ sed -i '/l3fwd_ipv6_route_array\[\].*{/,/^\}\;/c\\static struct l3fwd_ipv6_route l3fwd_ipv6_route_array[] = {\
+ {{1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 1},\
+ {{2,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 1},\
+ {{3,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 0},\
+ {{4,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 0},\
+ {{5,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 1},\
+ {{6,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 1},\
+ {{7,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 0},\
+ {{8,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}, 48, 0},\
+ };' examples/ip_fragmentation/main.c
+
+And re-compile examples/ip_fragmentation::
+
+ make -C examples/ip_fragmentation
+
Test Case 1: IP Fragmentation normal ip packet forward
======================================================
--
2.17.1
next prev parent reply other threads:[~2020-09-03 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 9:57 [dts] [PATCH V1 0/7] update " Xie wei
2020-09-03 9:57 ` [dts] [dts 1/7] test_plans/unit_tests_kni_test_plan:update " Xie wei
2020-09-03 9:57 ` [dts] [dts 2/7] test_plans/pmdpcap_test_plan:update " Xie wei
2020-09-03 9:57 ` [dts] [dts 3/7] test_plans/multicast_test_plan:update " Xie wei
2020-09-03 9:57 ` [dts] [dts 4/7] test_plans/kni_test_plan:update " Xie wei
2020-09-03 9:57 ` [dts] [dts 5/7] test_plans/ipv4_reassembly_test_plan:update " Xie wei
2020-09-03 9:57 ` Xie wei [this message]
2020-09-03 9:57 ` [dts] [dts 7/7] test_plans/efd_test_plan:update " Xie wei
2020-09-04 6:10 ` [dts] [PATCH V1 0/7] update " Ma, LihongX
2020-09-10 2:54 ` 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=20200903095746.32389-7-weix.xie@intel.com \
--to=weix.xie@intel.com \
--cc=dts@dpdk.org \
/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).