From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 24E35239 for ; Tue, 26 Feb 2019 03:55:36 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Feb 2019 18:55:36 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,413,1544515200"; d="scan'208";a="322096245" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga006.fm.intel.com with ESMTP; 25 Feb 2019 18:55:36 -0800 Received: from fmsmsx115.amr.corp.intel.com (10.18.116.19) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 25 Feb 2019 18:55:36 -0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx115.amr.corp.intel.com (10.18.116.19) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 25 Feb 2019 18:55:35 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.110]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.194]) with mapi id 14.03.0415.000; Tue, 26 Feb 2019 10:55:33 +0800 From: "Tu, Lijuan" To: Rami Rosen , "dts@dpdk.org" Thread-Topic: [dts] [PATCH] test_plan: fix DPDK project name Thread-Index: AQHUwjxwz9dXAmV6wkm41py6EN0twqXxePmA Date: Tue, 26 Feb 2019 02:55:33 +0000 Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA271B2@SHSMSX101.ccr.corp.intel.com> References: <20190211190243.13553-1-ramirose@gmail.com> In-Reply-To: <20190211190243.13553-1-ramirose@gmail.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.0.400.15 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjUxMTczNWQtNmJmNC00NWIzLWJiNGEtYThjMTE0MmU1OTgxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiaTJka09FN25ITFFHVHlDZStidW5waEhXMXNlVVVcL3dwWG1PNWZQZlJiZ3U4ZTZHblFKWlJSdlhOMGc0eWhYaDgifQ== 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] test_plan: fix DPDK project name 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: Tue, 26 Feb 2019 02:55:37 -0000 Applied, thanks > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Rami Rosen > Sent: Tuesday, February 12, 2019 3:03 AM > To: dts@dpdk.org > Cc: Rami Rosen > Subject: [dts] [PATCH] test_plan: fix DPDK project name >=20 > The DPDK project moved to the Linux Foundation quite a time ago. >=20 > https://www.linuxfoundation.org/Projects/dpdk/ >=20 > This patch removes usage of "Intel DPDK" from several test plans. >=20 > Signed-off-by: Rami Rosen > --- > test_plans/multiprocess_test_plan.rst | 4 ++-- > test_plans/stability_test_plan.rst | 4 ++-- > test_plans/unit_tests_eal_test_plan.rst | 2 +- > test_plans/vmdq_test_plan.rst | 4 ++-- > 4 files changed, 7 insertions(+), 7 deletions(-) >=20 > diff --git a/test_plans/multiprocess_test_plan.rst > b/test_plans/multiprocess_test_plan.rst > index 8598048..89abe6c 100644 > --- a/test_plans/multiprocess_test_plan.rst > +++ b/test_plans/multiprocess_test_plan.rst > @@ -42,7 +42,7 @@ Description > ----------- >=20 > This test is a basic multi-process test which demonstrates the basics of= sharing - > information between Intel DPDK processes. The same application binary is = run > +information between DPDK processes. The same application binary is run > twice - once as a primary instance, and once as a secondary instance. Me= ssages > are sent from primary to secondary and vice versa, demonstrating the proc= esses > are sharing memory and can communicate using rte_ring structures. > @@ -58,7 +58,7 @@ to the device under test:: > modprobe vfio-pci > usertools/dpdk-devbind.py --bind=3Dvfio-pci device_bus_id >=20 > -Assuming that an Intel DPDK build has been set up and the multi-process = sample > +Assuming that a DPDK build has been set up and the multi-process sample > applications have been built. >=20 > Test Case: Basic operation > diff --git a/test_plans/stability_test_plan.rst b/test_plans/stability_te= st_plan.rst > index 578f99e..c051954 100644 > --- a/test_plans/stability_test_plan.rst > +++ b/test_plans/stability_test_plan.rst > @@ -78,7 +78,7 @@ Test Case: Mix of different NIC types >=20 > Check that a mix of different NIC types is supported. The system should > recognize all the NICs that are part of the system and are supported by t= he -Intel > DPDK PMD. Check that ports from NICs of different type can send and > +DPDK PMD. Check that ports from NICs of different type can send and > receive traffic at the same time. >=20 > Recommended test configuration: testpmd application using a single logic= al > core @@ -88,7 +88,7 @@ two 10GbE ports (e.g. Intel 82599 NIC). > Test Case: Coexistence of kernel space drivers with Poll Mode Drivers > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 > -Verify that Intel DPDK PMD running in user space can work with the kerne= l > +Verify that DPDK PMD running in user space can work with the kernel > space space NIC drivers. >=20 > Recommended test configuration: testpmd application using a single logic= al > core diff --git a/test_plans/unit_tests_eal_test_plan.rst > b/test_plans/unit_tests_eal_test_plan.rst > index 33b0f14..7b2cf62 100644 > --- a/test_plans/unit_tests_eal_test_plan.rst > +++ b/test_plans/unit_tests_eal_test_plan.rst > @@ -286,7 +286,7 @@ Interrupts > Multiprocess > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > -Validates that a secondary Intel DPDK instance can be run alongside a pr= imary > when the appropriate EAL command-line flags are passed. Also validates th= at > secondary processes cannot interfere with primary processes by creating > memory objects, such as mempools or rings. > +Validates that a secondary DPDK instance can be run alongside a primary = when > the appropriate EAL command-line flags are passed. Also validates that > secondary processes cannot interfere with primary processes by creating > memory objects, such as mempools or rings. >=20 > String > =3D=3D=3D=3D=3D=3D > diff --git a/test_plans/vmdq_test_plan.rst b/test_plans/vmdq_test_plan.rs= t > index f261f5f..1f19e6f 100644 > --- a/test_plans/vmdq_test_plan.rst > +++ b/test_plans/vmdq_test_plan.rst > @@ -48,7 +48,7 @@ The feature itself works by: > user priority field within the VLAN tag and MAC address. >=20 > The VMDQ features are enabled in the ``vmdq`` example application -conta= ined > in the Intel DPDK, and this application should be used to validate > +contained in the DPDK, and this application should be used to validate > the feature. >=20 > Prerequisites > @@ -56,7 +56,7 @@ Prerequisites > - All tests assume a linuxapp setup. > - The port ids of the two 10G or 40G ports to be used for the testing ar= e > specified > in the commandline. it use a portmask. > -- The Intel DPDK is compiled for the appropriate target type in each cas= e, and > +- The DPDK is compiled for the appropriate target type in each case, > +and > the VMDQ example application is compiled and linked with that DPDK > instance > - Two ports are connected to the test system, one to be used for packet > -- > 2.19.2