From: Zhimin Huang <zhiminx.huang@intel.com>
To: dts@dpdk.org
Cc: Zhimin Huang <zhiminx.huang@intel.com>
Subject: [dts][PATCH V3 0/5] optimized pf/vf ice_ipfragment
Date: Tue, 24 May 2022 16:19:09 +0800 [thread overview]
Message-ID: <20220524081914.44538-1-zhiminx.huang@intel.com> (raw)
mismatch pkt should cover mismatch inputset pkts and mismatch pattern pkts.
so optimized test flow and add mismatch pkts.
1.rte_flow_common no need to send pkts with ipfragment.
2.add mismach inputset pkts and mismatch pattern pkts.
3.add more info about ipfragment rule.
Zhimin Huang (5):
tests/rte_flow_common:modify check mismatch pkts test
tests/ice_ip_fragment_rte_flow:extend mismatch pkts
test_plans/ice_ip_fragment_rte_flow:extend mismatch pkts
tests/ice_iavf_ip_fragment_rte_flow:extend mismatch pkts
test_plans/ice_iavf_ip_fragment_rte_flow:extend mismatch pkts
...ce_iavf_ip_fragment_rte_flow_test_plan.rst | 67 ++++++++++-------
.../ice_ip_fragment_rte_flow_test_plan.rst | 72 ++++++++++++-------
...TestSuite_ice_iavf_ip_fragment_rte_flow.py | 48 +++++++++----
tests/TestSuite_ice_ip_fragment_rte_flow.py | 60 ++++++++++++----
tests/rte_flow_common.py | 16 +++--
5 files changed, 184 insertions(+), 79 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-24 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 8:19 Zhimin Huang [this message]
2022-05-24 8:19 ` [dts][PATCH V3 1/5] tests/rte_flow_common:modify check mismatch pkts test Zhimin Huang
2022-05-24 8:19 ` [dts][PATCH V3 2/5] tests/ice_ip_fragment_rte_flow:extend mismatch pkts Zhimin Huang
2022-05-24 8:19 ` [dts][PATCH V3 3/5] test_plans/ice_ip_fragment_rte_flow:extend " Zhimin Huang
2022-05-24 8:19 ` [dts][PATCH V3 4/5] tests/ice_iavf_ip_fragment_rte_flow:extend " Zhimin Huang
2022-05-24 8:19 ` [dts][PATCH V3 5/5] test_plans/ice_iavf_ip_fragment_rte_flow:extend " Zhimin Huang
2022-05-25 11:08 ` lijuan.tu
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=20220524081914.44538-1-zhiminx.huang@intel.com \
--to=zhiminx.huang@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).