From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1 1/2] conf: add config file to support per patch performance of virtio
Date: Fri, 28 Feb 2020 02:06:42 +0000 [thread overview]
Message-ID: <21229fecabaf4536a8a3c3b0787d757d@intel.com> (raw)
In-Reply-To: <1582828567-674-2-git-send-email-lihongx.ma@intel.com>
Tested-by:ma,lihong<lihongx.ma@intel.com>
Regards,
Ma,lihong
-----Original Message-----
From: Ma, LihongX
Sent: Friday, February 28, 2020 2:36 AM
To: dts@dpdk.org
Cc: Ma, LihongX <lihongx.ma@intel.com>
Subject: [dts][PATCH V1 1/2] conf: add config file to support per patch performance of virtio
add config file for pvp_multi_paths_performance to test per patch performance
Signed-off-by: lihong <lihongx.ma@intel.com>
---
conf/pvp_multi_paths_performance.cfg | 6 ++++++
1 file changed, 6 insertions(+)
create mode 100644 conf/pvp_multi_paths_performance.cfg
diff --git a/conf/pvp_multi_paths_performance.cfg b/conf/pvp_multi_paths_performance.cfg
new file mode 100644
index 0000000..a725abb
--- /dev/null
+++ b/conf/pvp_multi_paths_performance.cfg
@@ -0,0 +1,6 @@
+[suite]
+update_expected = True
+test_parameters = {64: [1024],1518: [1024]} test_duration = 60
+accepted_tolerance = 2 expected_throughput =
+{'test_perf_pvp_virtio11_mergeable': {64: {1024: 0.00}, 1518: {1024:
+0.00}}, 'test_perf_pvp_virtio11_normal': {64: {1024: 0.00}, 1518:
+{1024: 0.00}}, 'test_perf_pvp_virtio11_inorder_mergeable': {64: {1024:
+0.00}, 1518: {1024: 0.00}}, 'test_perf_pvp_virtio11_inorder_normal':
+{64: {1024: 0.00}, 1518: {1024: 0.00}},
+'test_perf_pvp_inorder_mergeable': {64: {1024: 0.00}, 1518: {1024:
+0.00}}, 'test_perf_pvp_inorder_no_mergeable': {64: {1024: 0.00}, 1518:
+{1024: 0.00}},'test_perf_pvp_mergeable': {64: {1024: 0.00}, 1518:
+{1024: 0.00}},'test_perf_pvp_normal': {64: {1024: 0.00}, 1518: {1024:
+0.00}},'test_perf_pvp_vector_rx': {64: {1024: 0.00}, 1518: {1024:
+0.00}},}
--
2.7.4
next prev parent reply other threads:[~2020-02-28 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 18:36 [dts] [PATCH V1 0/2] support pvp_multi_paths_performance run per patch lihong
2020-02-27 18:36 ` [dts] [PATCH V1 1/2] conf: add config file to support per patch performance of virtio lihong
2020-02-28 2:06 ` Ma, LihongX [this message]
2020-02-27 18:36 ` [dts] [PATCH V1 2/2] tests/pvp_multi_paths_performance: modify code to support per patch performance lihong
2020-02-28 2:07 ` Ma, LihongX
2020-03-03 7:11 ` Tu, Lijuan
2020-03-03 9:00 ` Ma, LihongX
2020-02-28 2:07 ` [dts] [PATCH V1 0/2] support pvp_multi_paths_performance run per patch Ma, LihongX
2020-02-27 18:51 [dts] [PATCH V1 0/2] support pvp_multi_paths_virtio_single_core_performance " lihong
2020-02-27 18:51 ` [dts] [PATCH V1 1/2] conf: add config file to support per patch performance of virtio lihong
2020-02-28 2:22 ` Ma, LihongX
2020-02-27 22:41 [dts] [PATCH V1 0/2] support pvp_multi_paths_vhost_single_core_performance run per patch lihong
2020-02-27 22:41 ` [dts] [PATCH V1 1/2] conf: add config file to support per patch performance of virtio lihong
2020-02-28 6:11 ` Ma, LihongX
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=21229fecabaf4536a8a3c3b0787d757d@intel.com \
--to=lihongx.ma@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).