From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, hailinx.xu@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V6 0/3] flexible_rxd: add test cases for iavf/mpls
Date: Tue, 10 Nov 2020 14:18:55 +0800 [thread overview]
Message-ID: <20201110061858.5525-1-yufengx.mo@intel.com> (raw)
v6:
- update compile dep file name based on 20.11 rc3 change.
- upload iavf_flexible_descriptor suite script for flexible iavf merged in 20.11 rc3.
v5:
- rebase source code
v4:
- add non escape string limit.
v3:
- update compile dep file name based on 20.11 rc1 change.
v2:
- update iavf test content
- change the 'flex_desc' to 'proto_xtr' when start testpmd.
- change check_IPv4_IPv6_TCP_fields_in_RXD_on_specific_queues RXDIDs.
v1:
- add test cases for iavf/mpls.
yufengmx (3):
flexible_rxd: unify common test content
flexible_rxd: add mpls test cases
iavf_flexible_descriptor: upload suite
tests/TestSuite_flexible_rxd.py | 255 ++++-------
tests/TestSuite_iavf_flexible_descriptor.py | 246 ++++++++++
tests/flexible_common.py | 483 ++++++++++++++++++++
3 files changed, 825 insertions(+), 159 deletions(-)
create mode 100644 tests/TestSuite_iavf_flexible_descriptor.py
create mode 100644 tests/flexible_common.py
--
2.21.0
next reply other threads:[~2020-11-10 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 6:18 yufengmx [this message]
2020-11-10 6:18 ` [dts] [PATCH V6 1/3] flexible_rxd: unify common test content yufengmx
2020-11-18 6:43 ` Chen, Zhaoyan
2020-11-10 6:18 ` [dts] [PATCH V6 2/3] flexible_rxd: add mpls test cases yufengmx
2020-11-10 6:18 ` [dts] [PATCH V6 3/3] iavf_flexible_descriptor: upload suite yufengmx
2020-11-10 6:24 ` [dts] [PATCH V6 0/3] flexible_rxd: add test cases for iavf/mpls Mo, YufengX
2020-11-10 6:30 ` Xu, HailinX
2020-11-19 8:36 ` 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=20201110061858.5525-1-yufengx.mo@intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=hailinx.xu@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).