From: Peng Yuan <yuan.peng@intel.com>
To: dts@dpdk.org
Cc: Peng Yuan <yuan.peng@intel.com>
Subject: [dts] [PATCH]test_plans: add port information change
Date: Tue, 11 Aug 2020 14:49:14 +0000 [thread overview]
Message-ID: <1597157354-169781-1-git-send-email-yuan.peng@intel.com> (raw)
add port information change to flow_classify_softnic related config
files.
Signed-off-by: Peng Yuan <yuan.peng@intel.com>
diff --git a/test_plans/flow_classify_softnic_test_plan.rst b/test_plans/flow_classify_softnic_test_plan.rst
index 34984e10..b18d32b6 100644
--- a/test_plans/flow_classify_softnic_test_plan.rst
+++ b/test_plans/flow_classify_softnic_test_plan.rst
@@ -40,7 +40,9 @@ The SoftNIC allows building custom NIC pipelines in SW. The Soft NIC pipeline is
Prerequisites
=============
-The DUT must have four 10G Ethernet ports connected to four ports on tester that are controlled by the Scapy packet generator::
+The DUT can have 4*10G Ethernet ports or 2*10G Ethernet ports.
+We design case with 4*10G Ethernet ports.
+The DUT have four 10G Ethernet ports connected to four ports on tester that are controlled by the Scapy packet generator::
dut_port_0 <---> tester_port_0
dut_port_1 <---> tester_port_1
@@ -59,6 +61,14 @@ Bind them to dpdk igb_uio driver::
./usertools/dpdk-devbind.py -b igb_uio 05:00.0 05:00.1 05:00.2 05:00.3
Change ./drivers/net/softnic/firmware.cli to meet the specific test environment.
+Change ports info to your actual ports info::
+
+ link LINK0 dev 0000:05:00.0
+ link LINK1 dev 0000:05:00.1
+ link LINK2 dev 0000:05:00.2
+ link LINK3 dev 0000:05:00.3
+
+Other changes are shown in each case.
Start softnic with following command line::
--
2.17.1
next reply other threads:[~2020-08-11 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 14:49 Peng Yuan [this message]
2020-08-13 3:05 ` 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=1597157354-169781-1-git-send-email-yuan.peng@intel.com \
--to=yuan.peng@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).