From: Haiyang Zhao <haiyangx.zhao@intel.com>
To: dts@dpdk.org
Cc: Haiyang Zhao <haiyangx.zhao@intel.com>
Subject: [dts] [PATCH V1 09/14] test_plans/pvp_multi_paths_performance: fix build warnings and errors
Date: Tue, 23 Jun 2020 10:21:36 +0800 [thread overview]
Message-ID: <1592878901-216102-10-git-send-email-haiyangx.zhao@intel.com> (raw)
In-Reply-To: <1592878901-216102-1-git-send-email-haiyangx.zhao@intel.com>
Signed-off-by: Haiyang Zhao <haiyangx.zhao@intel.com>
---
test_plans/pvp_multi_paths_performance_test_plan.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/test_plans/pvp_multi_paths_performance_test_plan.rst b/test_plans/pvp_multi_paths_performance_test_plan.rst
index c35b0e4..74b050a 100644
--- a/test_plans/pvp_multi_paths_performance_test_plan.rst
+++ b/test_plans/pvp_multi_paths_performance_test_plan.rst
@@ -38,10 +38,12 @@ Benchmark PVP multi-paths performance with 10 tx/rx paths. Includes mergeable, n
inorder mergeable, inorder non-mergeable, virtio 1.1 mergeable, virtio 1.1 non-mergeable，virtio 1.1 inorder
mergeable, virtio 1.1 inorder non-mergeable, virtio1.1 vectorized path. Give 1 core for vhost and virtio respectively.
Packed ring vectorized path need:
+
AVX512F and required extensions are supported by compiler and host
VERSION_1 and IN_ORDER features are negotiated
mergeable feature is not negotiated
LRO offloading is disabled
+
Split ring vectorized rx path need:
mergeable and IN_ORDER features are not negotiated
LRO, chksum and vlan strip offloadings are disabled
--
1.8.3.1
next prev parent reply other threads:[~2020-06-23 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 2:21 [dts] [PATCH V1 00/14] test_plans: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 01/14] test_plans/cvl_advanced_iavf_rss: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 02/14] test_plans/cvl_fdir: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 03/14] test_plans/fortville_rss_input: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 04/14] test_plans/generic_flow_api: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 05/14] test_plans/iavf_fdir: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 06/14] test_plans/iavf_package_driver_error_handle: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 07/14] test_plans/l2tp_esp_coverage: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 08/14] test_plans/loopback_virtio_user_server_mode: " Haiyang Zhao
2020-06-23 2:21 ` Haiyang Zhao [this message]
2020-06-23 2:21 ` [dts] [PATCH V1 10/14] test_plans/pvp_multi_paths_virtio_single_core_performance: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 11/14] test_plans/rss_to_rte_flow: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 12/14] test_plans/stats_checks: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 13/14] test_plans/vm2vm_virtio_net_perf: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 14/14] test_plans/index: " Haiyang Zhao
2020-06-28 6:44 ` [dts] [PATCH V1 00/14] test_plans: " Tu, Lijuan
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=1592878901-216102-10-git-send-email-haiyangx.zhao@intel.com \
--to=haiyangx.zhao@intel.com \
--cc=dts@dpdk.org \
/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).