From: Yong Liu <yong.liu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH] fix bug that packet type detect failure
Date: Tue, 21 Jul 2015 10:12:39 +0800 [thread overview]
Message-ID: <1437444759-11565-1-git-send-email-yong.liu@intel.com> (raw)
From: Marvin Liu <yong.liu@intel.com>
Packet type value changed after unified packet type. So suite need
modification as consequence.
Signed-off-by: Marvin Liu <yong.liu@intel.com>
diff --git a/tests/TestSuite_nvgre.py b/tests/TestSuite_nvgre.py
index 62bb83b..954259d 100644
--- a/tests/TestSuite_nvgre.py
+++ b/tests/TestSuite_nvgre.py
@@ -163,14 +163,14 @@ class NvgreTestConfig(object):
"""
if self.outer_ip_proto != 47:
if self.outer_l3_type == 'IPv4':
- return 'PKT_RX_IPV4_HDR'
+ return '(outer) L3 type: IPV4_EXT_UNKNOWN'
else:
- return 'PKT_RX_IPV6_HDR'
+ return '(outer) L3 type: IPV6_EXT_UNKNOWN'
else:
- if self.outer_l3_type == 'IPv4':
- return 'PKT_RX_TUNNEL_IPV4_HDR'
+ if self.inner_l3_type == 'IPv4':
+ return 'Inner L3 type: IPV4_EXT_UNKNOWN'
else:
- return 'PKT_RX_TUNNEL_IPV6_HDR'
+ return 'Inner L3 type: IPV6_EXT_UNKNOWN'
def create_pcap(self, scp=True):
"""
diff --git a/tests/TestSuite_vxlan.py b/tests/TestSuite_vxlan.py
index 9dd7862..91da7ca 100644
--- a/tests/TestSuite_vxlan.py
+++ b/tests/TestSuite_vxlan.py
@@ -90,14 +90,14 @@ class VxlanTestConfig(object):
"""
if self.outer_udp_dst != VXLAN_PORT:
if self.outer_ip6_src != 'N/A':
- return 'PKT_RX_IPV6_HDR'
+ return '(outer) L3 type: IPV6_EXT_UNKNOWN'
else:
- return 'PKT_RX_IPV4_HDR'
+ return '(outer) L3 type: IPV4_EXT_UNKNOWN'
else:
- if self.outer_ip6_src != 'N/A':
- return 'PKT_RX_TUNNEL_IPV6_HDR'
+ if self.inner_ip6_src != 'N/A':
+ return 'Inner L3 type: IPV6_EXT_UNKNOWN'
else:
- return 'PKT_RX_TUNNEL_IPV4_HDR'
+ return 'Inner L3 type: IPV4_EXT_UNKNOWN'
def create_pcap(self, scp=True):
"""
--
1.9.3
reply other threads:[~2015-07-21 2:12 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=1437444759-11565-1-git-send-email-yong.liu@intel.com \
--to=yong.liu@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).