test suite reviews and discussions
 help / color / mirror / Atom feed
From: lihong <lihongx.ma@intel.com>
To: dts@dpdk.org
Cc: lihong <lihongx.ma@intel.com>
Subject: [dts] [PATCH V1 1/2] conf: add config file to support per patch performance of virtio
Date: Fri, 28 Feb 2020 02:51:59 +0800	[thread overview]
Message-ID: <1582829520-1014-2-git-send-email-lihongx.ma@intel.com> (raw)
In-Reply-To: <1582829520-1014-1-git-send-email-lihongx.ma@intel.com>

add config file pvp_multi_paths_virtio_single_core_performance.cfg to
support suite run per patch performance

Signed-off-by: lihong <lihongx.ma@intel.com>
---
 conf/pvp_multi_paths_virtio_single_core_performance.cfg | 6 ++++++
 1 file changed, 6 insertions(+)
 create mode 100644 conf/pvp_multi_paths_virtio_single_core_performance.cfg

diff --git a/conf/pvp_multi_paths_virtio_single_core_performance.cfg b/conf/pvp_multi_paths_virtio_single_core_performance.cfg
new file mode 100644
index 0000000..f7703a3
--- /dev/null
+++ b/conf/pvp_multi_paths_virtio_single_core_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_virtio_single_core_virtio11_mergeable': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_virtio11_normal': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_virtio11_inorder_mergeable': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_virtio11_inorder_normal': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_inorder_mergeable': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_inorder_no_mergeable': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_mergeable': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_normal': {64: {1024: 0.0}, 1518: {1024: 0.0}}, 'test_perf_virtio_single_core_vector_rx': {64: {1024: 0.0}, 1518: {1024: 0.0}}}
-- 
2.7.4


  reply	other threads:[~2020-02-28  2:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 18:51 [dts] [PATCH V1 0/2] support pvp_multi_paths_virtio_single_core_performance run per patch lihong
2020-02-27 18:51 ` lihong [this message]
2020-02-28  2:22   ` [dts] [PATCH V1 1/2] conf: add config file to support per patch performance of virtio Ma, LihongX
2020-02-27 18:52 ` [dts] [PATCH V1 2/2] tests/pvp_multi_paths_virtio_single_core_performance: modify code to support per patch performance lihong
2020-02-28  2:22   ` Ma, LihongX
2020-03-03  7:15   ` Tu, Lijuan
2020-02-28  2:22 ` [dts] [PATCH V1 0/2] support pvp_multi_paths_virtio_single_core_performance run per patch Ma, LihongX
  -- strict thread matches above, loose matches on Subject: below --
2020-02-27 22:41 [dts] [PATCH V1 0/2] support pvp_multi_paths_vhost_single_core_performance " 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
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

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=1582829520-1014-2-git-send-email-lihongx.ma@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).