From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, qi.fu@intel.com, ke1.xu@intel.com
Subject: [DTS][PATCH V2 0/2] update test plans and tests to support represented port action and port representor action from deprecated vf action in ice_qinq
Date: Wed, 7 Dec 2022 19:18:08 +0800 [thread overview]
Message-ID: <20221207111810.466634-1-ke1.xu@intel.com> (raw)
A new API is introduced to replace the VF actions in DPDK 22.11.
New API covers deprecated TO_VF action on DCFs by port representor and
represented port actions. These patches checks the existing use of vf id
action and vf original action and replace them with new API.
Method calling of launch_testpmd is updated to enable representor.
Testpmd args are modified to support appyling representors for the new API.
Rules are modified for the old API being deprecated, changing to the new API.
Ports id are modified corresponding to the port representors and modified API.
File names of packet capturing is renamed to .pcap to fix a no-reason
failure when using .cap
Ke Xu (2):
test_plans/ice_qinq: update test plan to support represented port
action from deprecated vf action
tests/ice_qinq: update test plan to support represented port action
from deprecated vf action
test_plans/ice_qinq_test_plan.rst | 106 +++++++++++++++---------------
tests/TestSuite_ice_qinq.py | 104 ++++++++++++++---------------
2 files changed, 105 insertions(+), 105 deletions(-)
--
2.25.1
next reply other threads:[~2022-12-07 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 11:18 Ke Xu [this message]
2022-12-07 11:18 ` [DTS][PATCH V2 1/2] test_plans/ice_qinq: update test plan to support represented port action from deprecated vf action Ke Xu
2022-12-07 11:18 ` [DTS][PATCH V2 2/2] tests/ice_qinq: " Ke Xu
2022-12-12 9:56 ` Li, HongboX
2022-12-13 6:14 ` 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=20221207111810.466634-1-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=qi.fu@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).