From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dts] [PATCH V2 0/2] support pvp_multi_paths_performanc run per patch performance
Date: Wed, 11 Mar 2020 04:31:41 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBEB984@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1583199061-12136-1-git-send-email-lihongx.ma@intel.com>
Applied the series, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Tuesday, March 3, 2020 9:31 AM
> To: dts@dpdk.org
> Cc: Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V2 0/2] support pvp_multi_paths_performanc run per
> patch performance
>
> * add config file and modify suite to support pvp_multi_paths_performanc
> check the throughput can reach value
>
> lihong (2):
> conf: add config file to support per patch performance
> 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 | 217
> ++++++++++++++++++++++---
> 2 files changed, 198 insertions(+), 25 deletions(-) create mode 100644
> conf/pvp_multi_paths_performance.cfg
>
> --
> 2.7.4
prev parent reply other threads:[~2020-03-11 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 1:30 lihong
2020-03-03 1:31 ` [dts] [PATCH V2 1/2] conf: add config file to support " lihong
2020-03-03 9:00 ` Ma, LihongX
2020-03-03 1:31 ` [dts] [PATCH V2 2/2] tests/pvp_multi_paths_performance: modify code " lihong
2020-03-03 9:01 ` Ma, LihongX
2020-03-03 9:01 ` [dts] [PATCH V2 0/2] support pvp_multi_paths_performanc run " Ma, LihongX
2020-03-11 4:31 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BBEB984@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@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).