test suite reviews and discussions
 help / color / mirror / Atom feed
From: Xie wei <weix.xie@intel.com>
To: dts@dpdk.org
Cc: Xie wei <weix.xie@intel.com>
Subject: [dts] [dts 3/7] test_plans/multicast_test_plan:update test plan to sync with testsuite
Date: Thu,  3 Sep 2020 17:57:42 +0800	[thread overview]
Message-ID: <20200903095746.32389-4-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/multicast_test_plan.rst | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

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
 ===================================
-- 
2.17.1


  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 ` Xie wei [this message]
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 ` [dts] [dts 6/7] test_plans/ipfrag_test_plan:update " Xie wei
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-4-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).