[3/7] test_plans/multicast_test_plan:update test plan to sync with testsuite

Message ID 20200903095746.32389-4-weix.xie@intel.com (mailing list archive)
State Accepted
Headers
Series update test plan to sync with testsuite |

Commit Message

Xie, WeiX Sept. 3, 2020, 9:57 a.m. UTC
  Signed-off-by: Xie wei <weix.xie@intel.com>
---
 test_plans/multicast_test_plan.rst | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
  

Patch

diff --git a/test_plans/multicast_test_plan.rst b/test_plans/multicast_test_plan.rst
index f52dd9c..a190170 100644
--- a/test_plans/multicast_test_plan.rst
+++ b/test_plans/multicast_test_plan.rst
@@ -195,6 +195,29 @@  P0 and P2 are used on testing machine):
 
 These flows do not change across the test cases.
 
+6.Modify multicast route table::
+
+    sed -i '/mcast_group_table\[\].*{/,/^\}\;/c\\static struct mcast_group_params mcast_group_table[] = {\
+    {RTE_IPV4(224,0,0,101),1},\
+    {RTE_IPV4(224,0,0,102),2},\
+    {RTE_IPV4(224,0,0,103),3},\
+    {RTE_IPV4(224,0,0,104),4},\
+    {RTE_IPV4(224,0,0,105),5},\
+    {RTE_IPV4(224,0,0,106),6},\
+    {RTE_IPV4(224,0,0,107),7},\
+    {RTE_IPV4(224,0,0,108),8},\
+    {RTE_IPV4(224,0,0,109),9},\
+    {RTE_IPV4(224,0,0,110),10},\
+    {RTE_IPV4(224,0,0,111),11},\
+    {RTE_IPV4(224,0,0,112),12},\
+    {RTE_IPV4(224,0,0,113),13},\
+    {RTE_IPV4(224,0,0,114),14},\
+    {RTE_IPV4(224,0,0,115),15},\
+    };' examples/ipv4_multicast/main.c
+
+And re-compile examples/ipv4_multicast::
+
+    make -C examples/ipv4_multicast
 
 Test Case: IP4 Multicast Forwarding
 ===================================