From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 3EF505587 for ; Fri, 18 Nov 2016 04:17:00 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP; 17 Nov 2016 19:16:59 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,655,1473145200"; d="scan'208";a="1070097761" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga001.fm.intel.com with ESMTP; 17 Nov 2016 19:16:59 -0800 Received: from fmsmsx154.amr.corp.intel.com (10.18.116.70) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 17 Nov 2016 19:16:59 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX154.amr.corp.intel.com (10.18.116.70) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 17 Nov 2016 19:16:59 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.239]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.138]) with mapi id 14.03.0248.002; Fri, 18 Nov 2016 11:16:57 +0800 From: "Xu, HuilongX" To: "Liu, Yong" , "dts@dpdk.org" Thread-Topic: [dts] [PATCH V1 2/3] update vxlan ipv4/ipv6 packet detect packet type info Thread-Index: AQHSQUjd6rRdET771UGIgoc7jKNN7KDeD1AQgAABNUA= Date: Fri, 18 Nov 2016 03:16:56 +0000 Message-ID: References: <1479438482-4875-1-git-send-email-huilongx.xu@intel.com> <1479438482-4875-2-git-send-email-huilongx.xu@intel.com> <86228AFD5BCD8E4EBFD2B90117B5E81E6032B5EE@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E6032B5EE@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V1 2/3] update vxlan ipv4/ipv6 packet detect packet type info X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 03:17:01 -0000 Hi yong, For outer packet layer, only use packet type output, but for inner layer wi= ll user INNER_ and packet type output in newest dpdk code. > -----Original Message----- > From: Liu, Yong > Sent: Friday, November 18, 2016 11:11 AM > To: Xu, HuilongX; dts@dpdk.org > Cc: Xu, HuilongX > Subject: RE: [dts] [PATCH V1 2/3] update vxlan ipv4/ipv6 packet detect > packet type info >=20 >=20 >=20 > > -----Original Message----- > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,huilong > > Sent: Friday, November 18, 2016 11:08 AM > > To: dts@dpdk.org > > Cc: Xu, HuilongX > > Subject: [dts] [PATCH V1 2/3] update vxlan ipv4/ipv6 packet detect > packet > > type info > > > > Signed-off-by: xu,huilong > > --- > > tests/TestSuite_nvgre.py | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/tests/TestSuite_nvgre.py b/tests/TestSuite_nvgre.py > > index c1df309..015aa9f 100644 > > --- a/tests/TestSuite_nvgre.py > > +++ b/tests/TestSuite_nvgre.py > > @@ -164,14 +164,14 @@ class NvgreTestConfig(object): > > """ > > if self.outer_ip_proto !=3D 47: > > if self.outer_l3_type =3D=3D 'IPv4': > > - return '(outer) L3 type: IPV4_EXT_UNKNOWN' > > + return 'L3_IPV4_EXT_UNKNOWN' >=20 > If outer and inner packet layer use same string, we can't distinguish > between them. > What cause the output message change? >=20 > > else: > > - return '(outer) L3 type: IPV6_EXT_UNKNOWN' > > + return 'L3_IPV6_EXT_UNKNOWN' > > else: > > if self.inner_l3_type =3D=3D 'IPv4': > > - return 'Inner L3 type: IPV4_EXT_UNKNOWN' > > + return 'L3_IPV4_EXT_UNKNOWN' > > else: > > - return 'Inner L3 type: IPV6_EXT_UNKNOWN' > > + return 'L3_IPV6_EXT_UNKNOWN' > > > > def create_pcap(self): > > """ > > -- > > 1.9.3