From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lijuan.tu@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V4 0/4] l3fwd: support l3fwd pf&vf test scenario
Date: Fri, 10 Apr 2020 15:52:16 +0800 [thread overview]
Message-ID: <20200410075220.5184-1-yufengx.mo@intel.com> (raw)
support l3fwd pf&vf test scenario.
v4:
- rebase.
-
v3:
- close dpdk CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC compile flag when use vf.
v2:
- change pf_driver to be kernel driver.
- change vf_driver to be configured in execution.cfg.
- remove cases test_perf_vf_rfc2544_ipv4_em/test_perf_vf_throughput_ipv4_em.
- add case test_perf_vf_throughput_ipv4_lpm.
yufengmx (4):
conf/vf_l3fwd_base: stream flow configuration
conf/vf_l3fwd_kernelpf: suite testing configuration
tests/vf_l3fwd_kernelpf: upload automation script
vf_l3fwd: support l3fwd pf&vf test scenario
conf/vf_l3fwd_base.cfg | 14 +
conf/vf_l3fwd_kernelpf.cfg | 104 +++++++
tests/TestSuite_vf_l3fwd_kernelpf.py | 90 ++++++
tests/l3fwd_base.py | 405 +++++++++++++++++++++++----
4 files changed, 554 insertions(+), 59 deletions(-)
create mode 100644 conf/vf_l3fwd_base.cfg
create mode 100644 conf/vf_l3fwd_kernelpf.cfg
create mode 100644 tests/TestSuite_vf_l3fwd_kernelpf.py
--
2.21.0
next reply other threads:[~2020-04-10 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 7:52 yufengmx [this message]
2020-04-10 7:52 ` [dts] [PATCH V4 1/4] conf/vf_l3fwd_base: stream flow configuration yufengmx
2020-04-10 7:52 ` [dts] [PATCH V4 2/4] conf/vf_l3fwd_kernelpf: suite testing configuration yufengmx
2020-04-10 7:52 ` [dts] [PATCH V4 3/4] tests/vf_l3fwd_kernelpf: upload automation script yufengmx
2020-04-10 7:52 ` [dts] [PATCH V4 4/4] vf_l3fwd: support l3fwd pf&vf test scenario yufengmx
2020-04-20 4:43 ` [dts] [PATCH V4 0/4] l3fwd: " Tu, Lijuan
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=20200410075220.5184-1-yufengx.mo@intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@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).