From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1 0/4] add vswitch_pvp_multi_paths_performance_with_cbdma
Date: Fri, 22 Apr 2022 16:49:51 +0800 [thread overview]
Message-ID: <20220422084951.1562263-1-weix.ling@intel.com> (raw)
As commit 53d3f4778c(vhost: integrate dmadev in asynchronous data-path),
add new testsuite vswitch_pvp_multi_paths_performance_with_cbdma for
coverage the dpdk-vhost pvp multi paths performance test with cbdma.
1) Add new testplan vswitch_pvp_multi_paths_performance_with_cbdma_test_plan
into test_plans/index.rst.
2) Add new testplan
test_plans/vswitch_pvp_multi_paths_performance_with_cbdma_test_plan.
3) Add new testsuite
tests/vswitch_pvp_multi_paths_performance_with_cbdma.
4) Add testsuite config file
conf/vswitch_pvp_multi_paths_performance_with_cbdma.
Wei Ling (4):
test_plans/index: add vswitch_pvp_multi_paths_performance_with_cbdma
test_plans/vswitch_pvp_multi_paths_performance_with_cbdma_test_plan:
add vswitch_pvp_multi_paths_performance_with_cbdma testplan
tests/vswitch_pvp_multi_paths_performance_with_cbdma: add
vswitch_pvp_multi_paths_performance_with_cbdma new testsuite
conf/vswitch_pvp_multi_paths_performance_with_cbdma: add
vswitch_pvp_multi_paths_performance_with_cbdma config file
...pvp_multi_paths_performance_with_cbdma.cfg | 7 +
test_plans/index.rst | 1 +
...paths_performance_with_cbdma_test_plan.rst | 395 +++++++++++
..._pvp_multi_paths_performance_with_cbdma.py | 644 ++++++++++++++++++
4 files changed, 1047 insertions(+)
create mode 100644 conf/vswitch_pvp_multi_paths_performance_with_cbdma.cfg
create mode 100644 test_plans/vswitch_pvp_multi_paths_performance_with_cbdma_test_plan.rst
create mode 100644 tests/TestSuite_vswitch_pvp_multi_paths_performance_with_cbdma.py
--
2.25.1
reply other threads:[~2022-04-22 8:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220422084951.1562263-1-weix.ling@intel.com \
--to=weix.ling@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).