From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] test_plan: fix DPDK project name
Date: Tue, 26 Feb 2019 02:55:33 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA271B2@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190211190243.13553-1-ramirose@gmail.com>
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 <ramirose@gmail.com>
> Subject: [dts] [PATCH] test_plan: fix DPDK project name
>
> The DPDK project moved to the Linux Foundation quite a time ago.
>
> https://www.linuxfoundation.org/Projects/dpdk/
>
> This patch removes usage of "Intel DPDK" from several test plans.
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> 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(-)
>
> 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
> -----------
>
> 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. Messages
> are sent from primary to secondary and vice versa, demonstrating the processes
> 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=vfio-pci device_bus_id
>
> -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.
>
> Test Case: Basic operation
> diff --git a/test_plans/stability_test_plan.rst b/test_plans/stability_test_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
>
> 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 the -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.
>
> Recommended test configuration: testpmd application using a single logical
> core @@ -88,7 +88,7 @@ two 10GbE ports (e.g. Intel 82599 NIC).
> Test Case: Coexistence of kernel space drivers with Poll Mode Drivers
> =================================================================
> ====
>
> -Verify that Intel DPDK PMD running in user space can work with the kernel
> +Verify that DPDK PMD running in user space can work with the kernel
> space space NIC drivers.
>
> Recommended test configuration: testpmd application using a single logical
> 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
> ============
>
> -Validates that a secondary Intel 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.
> +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.
>
> String
> ======
> diff --git a/test_plans/vmdq_test_plan.rst b/test_plans/vmdq_test_plan.rst
> 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.
>
> The VMDQ features are enabled in the ``vmdq`` example application -contained
> 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.
>
> 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 are
> specified
> in the commandline. it use a portmask.
> -- The Intel DPDK is compiled for the appropriate target type in each case, 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
prev parent reply other threads:[~2019-02-26 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 19:02 Rami Rosen
2019-02-26 2:55 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BA271B2@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ramirose@gmail.com \
/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).