From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 71D52A0613 for ; Tue, 24 Sep 2019 11:18:40 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5B8C92BE1; Tue, 24 Sep 2019 11:18:40 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id F3A802BBB for ; Tue, 24 Sep 2019 11:18:37 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Sep 2019 02:18:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,543,1559545200"; d="scan'208";a="340023020" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga004.jf.intel.com with ESMTP; 24 Sep 2019 02:18:36 -0700 Received: from fmsmsx605.amr.corp.intel.com (10.18.126.85) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 24 Sep 2019 02:18:36 -0700 Received: from fmsmsx605.amr.corp.intel.com (10.18.126.85) by fmsmsx605.amr.corp.intel.com (10.18.126.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 24 Sep 2019 02:18:36 -0700 Received: from shsmsx108.ccr.corp.intel.com (10.239.4.97) by fmsmsx605.amr.corp.intel.com (10.18.126.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1713.5 via Frontend Transport; Tue, 24 Sep 2019 02:18:35 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.92]) by SHSMSX108.ccr.corp.intel.com ([169.254.8.146]) with mapi id 14.03.0439.000; Tue, 24 Sep 2019 17:18:34 +0800 From: "Tu, Lijuan" To: "Li, WenjieX A" , "dts@dpdk.org" CC: "Li, WenjieX A" Thread-Topic: [dts] [PATCH V2] test_plans:fix build warning Thread-Index: AQHVcbtF9jJe2oajHkCD1LT4T8UiA6c6jpRw Date: Tue, 24 Sep 2019 09:18:34 +0000 Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB27747@SHSMSX101.ccr.corp.intel.com> References: <1569207948-78383-1-git-send-email-wenjiex.a.li@intel.com> In-Reply-To: <1569207948-78383-1-git-send-email-wenjiex.a.li@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZmQ5MzM3M2YtZmZlMy00NzgxLWI2NDQtM2FhNzQ4OThjNzEyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiSmM2TzBxQkZ4Q0drXC9zbkZrVDM2SjdoNVV5SzdwNmtjTGFHcUszcGZNSXZuSk9ISkhwd0djRzFuc1BMMFVMYkIifQ== 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 V2] test_plans:fix build warning 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: , Errors-To: dts-bounces@dpdk.org Sender: "dts" Applied, thanks > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li > Sent: Monday, September 23, 2019 11:06 AM > To: dts@dpdk.org > Cc: Li, WenjieX A > Subject: [dts] [PATCH V2] test_plans:fix build warning >=20 > fix build warning >=20 > Signed-off-by: Wenjie Li > V2: fix "1 line adds whitespace errors." > 0001-test_plans-fix-build-warning.patch:26: trailing whitespace. > (b) Windriver TS 2 or CentOS 7 operating systems > warning: 1 line adds whitespace errors. >=20 >=20 > --- > test_plans/bbdev_test_plan.rst | 6 +++++- > test_plans/index.rst | 7 ++++++- > test_plans/sriov_kvm_test_plan.rst | 14 ++++++++++---- > 3 files changed, 21 insertions(+), 6 deletions(-) >=20 > diff --git a/test_plans/bbdev_test_plan.rst b/test_plans/bbdev_test_plan.= rst > index 800e7f6..7fa0e2a 100644 > --- a/test_plans/bbdev_test_plan.rst > +++ b/test_plans/bbdev_test_plan.rst > @@ -67,12 +67,14 @@ Prerequisites > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > 1. OS and Hardware > + > (a) An AVX2 supporting machine > - (b) Windriver TS 2 or CentOS 7 operating systems > + (b) Windriver TS 2 or CentOS 7 operating systems > (Fedora 25 and Ubuntu 16.04 is ok.) > (c) Intel ICC compiler installed >=20 > 2. FlexRAN SDK Libraries > + > To build DPDK with the *turbo_sw* PMD the user is required to downloa= d > the export controlled ``FlexRAN SDK`` Libraries. > An account at Intel Resource Design Center needs to be registered fro= m > @@ -84,6 +86,7 @@ Prerequisites > You can refer to the file dpdk/doc/guides/bbdevs/turbo_sw.rst. >=20 > 3. PMD setting > + > Current BBDEV framework is en-suited with two vdev PMD drivers: > null and turbo_sw. > 1) Null PMD is similar to cryptodev Null PMD, which is an empty drive= r to > @@ -101,6 +104,7 @@ Prerequisites > They are both located in the build configuration file ``common_base``= . >=20 > 4. Test tool > + > A test suite for BBDEV is packaged with the framework to ease the > validation needs for various functions and use cases. > The tool to use for validation and testing is called: test-bbdev, dif= f --git > a/test_plans/index.rst b/test_plans/index.rst index 28f5a69..e15823e 1006= 44 > --- a/test_plans/index.rst > +++ b/test_plans/index.rst > @@ -133,6 +133,7 @@ The following are the test plans for the DPDK DTS > automated test system. > compressdev_qat_pmd_test_plan > compressdev_zlib_pmd_test_plan > enable_package_download_in_ice_driver_test_plan > + multicast_test_plan >=20 > veb_switch_test_plan > vf_daemon_test_plan > @@ -151,7 +152,6 @@ The following are the test plans for the DPDK DTS > automated test system. > vhost_multi_queue_qemu_test_plan > vhost_pmd_xstats_test_plan > vhost_qemu_mtu_test_plan > - vhost_tso_test_plan > vhost_user_live_migration_test_plan > vm_power_manager_test_plan > vmdq_test_plan > @@ -230,3 +230,8 @@ The following are the test plans for the DPDK DTS > automated test system. > iavf_test_plan > packet_capture_test_plan > packet_ordering_test_plan > + bbdev_test_plan > + performance_thread_test_plan > + > + fips_cryptodev_test_plan > + flow_filtering_test_plan > \ No newline at end of file > diff --git a/test_plans/sriov_kvm_test_plan.rst > b/test_plans/sriov_kvm_test_plan.rst > index f22b2ed..1b84f78 100644 > --- a/test_plans/sriov_kvm_test_plan.rst > +++ b/test_plans/sriov_kvm_test_plan.rst > @@ -135,7 +135,7 @@ Send 10 packets with VF0 mac address and make > sure the packets will be forwarded by VF1. >=20 > Test Case2: Mirror Traffic between 2VMs with Pool up mirroring - > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Set up common 2VM prerequisites. >=20 > @@ -216,7 +216,7 @@ After test need reset mirror rule:: > PF testpmd-> reset port 0 mirror-rule 0 >=20 > Test Case6: Mirror Traffic between 2VMs with Vlan mirroring - > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Set up common 2VM prerequisites. >=20 > @@ -237,7 +237,7 @@ After test need reset mirror rule:: > PF testpmd-> reset port 0 mirror-rule 0 >=20 > Test Case7: Mirror Traffic between 2VMs with up link mirroring & down li= nk > mirroring - > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts:: >=20 > @@ -247,9 +247,12 @@ Run testpmd on VM0 and VM1 and start traffic > forward on the VM hosts:: > When mirroring only between two Vfs, pool up (or down) mirroring and up > (or down) link mirroring lead to the same behavior, so we randomly choos= e > one way to mirror in both up and down directions. > up link mirroring as below: > + > 1. Pool up mirroring (Case 2) > 2. Uplink port mirroring(Case 4) > + > down link mirroring as below: > + > 1. Pool down mirroring(Fortville only, Case 3) > 2. Downlink port mirroring(Case 5) >=20 > @@ -274,7 +277,7 @@ After test need reset mirror rule:: > PF testpmd-> reset port 0 mirror-rule 1 >=20 > Test Case8: Mirror Traffic between 2VMs with Vlan & with up link mirrori= ng > & down link mirroring - > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >=20 > Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts:: >=20 > @@ -284,9 +287,12 @@ Run testpmd on VM0 and VM1 and start traffic > forward on the VM hosts:: > When mirroring only between two Vfs, pool up (or down) mirroring and up > (or down) link mirroring lead to the same behavior, so we randomly choos= e > one way to mirror in both up and down directions. > up link mirroring as below: > + > 1. Pool up mirroring (Case 2) > 2. Uplink port mirroring(Case 4) > + > down link mirroring as below: > + > 1. Pool down mirroring(Fortville only, Case 3) > 2. Downlink port mirroring(Case 5) >=20 > -- > 2.17.2