test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1 0/2] support pvp_multi_paths_performance run per patch
Date: Fri, 28 Feb 2020 02:07:00 +0000	[thread overview]
Message-ID: <023a33845f43419eb049e902df5e9fde@intel.com> (raw)
In-Reply-To: <1582828567-674-1-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 0/2] support pvp_multi_paths_performance run per patch

*add config file and modify suite to support pvp_multi_paths_performance to check throughput can reach expected.

lihong (2):
  conf: add config file to support per patch performance of virtio
  tests/pvp_multi_paths_performance: modify code to support per patch
    performance

 conf/pvp_multi_paths_performance.cfg           |   6 +
 tests/TestSuite_pvp_multi_paths_performance.py | 218 ++++++++++++++++++++++---
 2 files changed, 199 insertions(+), 25 deletions(-)  create mode 100644 conf/pvp_multi_paths_performance.cfg

--
2.7.4


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 18:36 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
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 ` Ma, LihongX [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=023a33845f43419eb049e902df5e9fde@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).