From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhao, XinfengX" <xinfengx.zhao@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
Subject: Re: [dts] [PATCH V1 0/6] rework cryptodev test script and conf
Date: Fri, 19 Jun 2020 03:32:40 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC5FA0D@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200604005445.110297-1-xinfengx.zhao@intel.com>
Applied the series, thanks
-----Original Message-----
From: dts <dts-bounces@dpdk.org> On Behalf Of xinfengx
Sent: 2020年6月4日 8:55
To: dts@dpdk.org
Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
Subject: [dts] [PATCH V1 0/6] rework cryptodev test script and conf
conf: simplify conf settings for cryptodev test
tests/cryptodev_common: improve cryptodev common methods
tests/crypto_perf_cryptodev_perf: rework crypto_perf test script
tests/l2fwd_cryptodev_func: rework l2fwd_crypto test script
tests/ipsec_gw_cryptodev_func: rework cryptodev ipsec test script
tests/unit_tests_cryptodev_func: rework cryptodev unit test script
conf/crypto_perf_cryptodev_perf.cfg | 115 +-
conf/cryptodev_sample.cfg | 6 +
conf/ipsec_gw_cryptodev_func.cfg | 156 +--
conf/l2fwd_cryptodev_func.cfg | 35 -
conf/unit_tests_cryptodev_func.cfg | 11 -
tests/TestSuite_crypto_perf_cryptodev_perf.py | 628 ++++------
tests/TestSuite_ipsec_gw_cryptodev_func.py | 624 ++--------
tests/TestSuite_l2fwd_cryptodev_func.py | 1036 ++++-------------
tests/TestSuite_unit_tests_cryptodev_func.py | 56 +-
tests/cryptodev_common.py | 117 +-
10 files changed, 785 insertions(+), 1999 deletions(-) create mode 100644 conf/cryptodev_sample.cfg delete mode 100644 conf/l2fwd_cryptodev_func.cfg delete mode 100644 conf/unit_tests_cryptodev_func.cfg
--
2.17.1
prev parent reply other threads:[~2020-06-19 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 0:54 xinfengx
2020-06-04 0:54 ` [dts] [PATCH V1 1/6] conf: simplify conf settings for cryptodev test xinfengx
2020-06-04 0:54 ` [dts] [PATCH V1 2/6] tests/cryptodev_common: improve cryptodev common methods xinfengx
2020-06-04 0:54 ` [dts] [PATCH V1 3/6] tests/crypto_perf_cryptodev_perf: rework crypto_perf test script xinfengx
2020-06-04 0:54 ` [dts] [PATCH V1 4/6] tests/l2fwd_cryptodev_func: rework l2fwd_crypto " xinfengx
2020-06-04 0:54 ` [dts] [PATCH V1 5/6] tests/ipsec_gw_cryptodev_func: rework cryptodev ipsec " xinfengx
2020-06-04 0:54 ` [dts] [PATCH V1 6/6] tests/unit_tests_cryptodev_func: rework cryptodev unit " xinfengx
2020-06-12 1:46 ` Wan, Zhe
2020-06-04 0:59 ` [dts] [PATCH V1 0/6] rework cryptodev test script and conf Zhao, XinfengX
2020-06-19 3:32 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC5FA0D@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=xinfengx.zhao@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).