From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1 1/2] test_plans/eventdev_pipeline_perf: fix build warnings
Date: Thu, 13 Jun 2019 09:11:16 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BABD07E@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1560330010-2936-1-git-send-email-wenjiex.a.li@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Wednesday, June 12, 2019 5:00 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V1 1/2] test_plans/eventdev_pipeline_perf: fix build
> warnings
>
> fix some build warnings.
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> .../eventdev_pipeline_perf_test_plan.rst | 31 +++++++++++++------
> 1 file changed, 21 insertions(+), 10 deletions(-)
>
> diff --git a/test_plans/eventdev_pipeline_perf_test_plan.rst
> b/test_plans/eventdev_pipeline_perf_test_plan.rst
> index 619f9a3..0cd9110 100644
> --- a/test_plans/eventdev_pipeline_perf_test_plan.rst
> +++ b/test_plans/eventdev_pipeline_perf_test_plan.rst
> @@ -31,10 +31,12 @@ echo 24 > /proc/sys/vm/nr_hugepages Configure
> limits of Eventdev devices ====================================
> Set all eventdev devices sso and ssow limits to zero. Then set eventdev
> device under tests sso and ssow limits to non-zero values as per
> cores/queues requriments ::
> +
> echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/sso
> echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/ssow
>
> Example ::
> +
> echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/tim
> echo 1 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/npa
> echo 16 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/sso
> @@ -51,7 +53,8 @@ Description: Execute performance test with Atomic_atq
> type of stage in multi-flo
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device_bus_id -- -w 0xc00000 -n=0 --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -74,7 +77,8 @@ Description: Execute performance test with Parallel_atq
> type of stage in multi-f
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device_bus_id -- -w 0xc00000 -n=0 -p --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -98,7 +102,8 @@ Description: Execute performance test with
> Ordered_atq type of stage in multi-fl
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device_bus_id -- -w 0xc00000 -n=0 -o --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -122,7 +127,8 @@ Description: Execute performance test with
> Atomic_atq type of stage in multi-flo
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=0 --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -145,7 +151,8 @@ Description: Execute performance test with
> Parallel_atq type of stage in multi-f
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=0 -p --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -169,7 +176,8 @@ Description: Execute performance test with
> Ordered_atq type of stage in multi-fl
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=0 -o --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -193,7 +201,8 @@ Description: Execute performance test with
> Atomic_atq type of stage in multi-flo
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id -
> - -w 0xc00000 -n=0 --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -216,7 +225,8 @@ Description: Execute performance test with
> Parallel_atq type of stage in multi-f
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id -
> - -w 0xc00000 -n=0 -p --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -240,7 +250,8 @@ Description: Execute performance test with
> Ordered_atq type of stage in multi-fl
>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id -
> - -w 0xc00000 -n=0 -o --dump
>
> - Parameters:
> + Parameters::
> +
> -c, COREMASK : Hexadecimal bitmask of cores to run on
> -w, --pci-whitelist : Add a PCI device in white list.
> Only use the specified PCI devices. The argument format
> @@ -254,4 +265,4 @@ Description: Execute performance test with
> Ordered_atq type of stage in multi-fl
>
> 2. Use Ixia to send huge number of packets(with same 5-tuple and different
> 5-tuple)
>
> -3. Observe the speed of packets received(Rx-rate) on Ixia.
> +3. Observe the speed of packets received(Rx-rate) on Ixia.
> \ No newline at end of file
> --
> 2.17.2
prev parent reply other threads:[~2019-06-13 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 9:00 Wenjie Li
2019-06-12 9:00 ` [dts] [PATCH V1 2/2] test_plans/index: append eventdev_pipeline_perf Wenjie Li
2019-06-13 9:11 ` Tu, Lijuan
2019-06-13 9:11 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BABD07E@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=wenjiex.a.li@intel.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).