From: "zhu,shuai" <shuaix.zhu@intel.com>
To: dts@dpdk.org
Cc: "zhu,shuai" <shuaix.zhu@intel.com>
Subject: [dts] [PATCH V1] test_plans/uni_pkt:Modify the naming of the NIC.
Date: Thu, 21 Feb 2019 16:59:41 +0800 [thread overview]
Message-ID: <1550739581-46203-1-git-send-email-shuaix.zhu@intel.com> (raw)
Modify the naming of the NIC in combination with the case.
Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
---
test_plans/uni_pkt_test_plan.rst | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/test_plans/uni_pkt_test_plan.rst b/test_plans/uni_pkt_test_plan.rst
index 905e27a..d458285 100644
--- a/test_plans/uni_pkt_test_plan.rst
+++ b/test_plans/uni_pkt_test_plan.rst
@@ -51,7 +51,7 @@ Enable ABI and disable vector ixgbe driver in dpdk configuration file.
Plug in three different types of nic on the board.
1x Intel® XL710-DA2 (Eagle Fountain)
1x Intel® 82599 Gigabit Ethernet Controller
-1x Intel® I350 Gigabit Network Connection
+1x Intel® powerville Gigabit Network Connection
Start testpmd and then enable rxonly and verbose mode::
@@ -95,7 +95,7 @@ Test Case: IPv4&L4 packet type detect
This case checked that whether L3 and L4 packet can be normally detected.
Only Fortville can detect icmp packet.
-Only niantic and i350 can detect ipv4 extension packet.
+Only niantic and powerville can detect ipv4 extension packet.
Fortville did not detect whether packet contain ipv4 header options, so L3
type will be shown as IPV4_EXT_UNKNOWN.
Fortville will identify all unrecognized L4 packet as L4_NONFRAG.
@@ -141,14 +141,14 @@ Send IP fragment+TCP packet and verify L2/L3/L4 corrected(Fortville)::
(outer) L3 type: IPV4_EXT_UNKNOWN
(outer) L4 type: L4_FRAG
-Send IP extension packet and verify L2/L3 corrected(Niantic,i350)::
+Send IP extension packet and verify L2/L3 corrected(Niantic,powerville)::
sendp([Ether()/IP(ihl=10)/Raw('\0'*40)],iface=txItf)
(outer) L3 type: IPV4_EXT
(outer) L4 type: Unknown
-Send IP extension+SCTP packet and verify L2/L3/L4 corrected(Niantic,i350)::
+Send IP extension+SCTP packet and verify L2/L3/L4 corrected(Niantic,powerville)::
sendp([Ether()/IP(ihl=10)/SCTP()/Raw('\0'*40)],iface=txItf)
@@ -191,7 +191,7 @@ Send IPv6 fragment packet and verify L2/L3/L4 corrected(Fortville)::
(outer) L3 type: IPV6_EXT_UNKNOWN
(outer) L4 type: L4_FRAG
-Send IPv6 fragment packet and verify L2/L3/L4 corrected(Niantic,i350)::
+Send IPv6 fragment packet and verify L2/L3/L4 corrected(Niantic,powerville)::
sendp([Ether()/IPv6()/IPv6ExtHdrFragment()/Raw('\0'*60)],iface=txItf)
@@ -283,11 +283,11 @@ Send IPv4+IPv6+ICMP packet and verify inner and outer L2/L3/L4 corrected::
Inner L4 type: ICMP
-Test Case: IPv6 in IPv4 tunnel packet type detect by niantic and i350
+Test Case: IPv6 in IPv4 tunnel packet type detect by niantic and powerville
=====================================================================
This case checked that whether IPv4 in IPv6 tunnel packet can be normally
-detected by Niantic and i350.
+detected.
Send IPv4+IPv6 packet and verify inner and outer L2/L3/L4 corrected::
@@ -336,6 +336,7 @@ Send IPv4+IPv6_EXT+TCP packet and verify inner and outer L2/L3/L4 corrected::
Inner L4 type: TCP
+
Test Case: IP in IPv6 tunnel packet type detect
===============================================
--
2.17.2
reply other threads:[~2019-02-21 8:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1550739581-46203-1-git-send-email-shuaix.zhu@intel.com \
--to=shuaix.zhu@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).