* [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle
@ 2022-11-30 3:53 Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 1/3] test_plans/dcf_lifecycle: update test plan to support represented port action from deprecated vf action Ke Xu
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: Ke Xu @ 2022-11-30 3:53 UTC (permalink / raw)
To: dts; +Cc: lijuan.tu, Ke Xu
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.
New fields are added in setup for applying representor to the case.
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.
Duplicated whitespaces are removed and extra whitespaces are added to formate
the document.
Jin Ling (3):
test_plans/dcf_lifecycle: update test plan to support represented port
action from deprecated vf action
test_plans/dcf_lifecycle: remove redundant white space
tests/dcf_lifecycle: update test plan to support represented port
action from deprecated vf action
test_plans/dcf_lifecycle_test_plan.rst | 196 ++++++++++++-------------
tests/TestSuite_dcf_lifecycle.py | 24 +--
2 files changed, 110 insertions(+), 110 deletions(-)
--
2.25.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* [DTS][PATCH V1 1/3] test_plans/dcf_lifecycle: update test plan to support represented port action from deprecated vf action
2022-11-30 3:53 [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Ke Xu
@ 2022-11-30 3:53 ` Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 2/3] test_plans/dcf_lifecycle: remove redundant white space Ke Xu
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Ke Xu @ 2022-11-30 3:53 UTC (permalink / raw)
To: dts; +Cc: lijuan.tu, Ke Xu, Jin Ling
A new API is introduced to replace the VF actions in DPDK 22.11. To support This
new API, several modifications are made.
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.
Duplicated whitespaces are removed.
Signed-off-by: Jin Ling <jin.ling@intel.com>
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
test_plans/dcf_lifecycle_test_plan.rst | 84 +++++++++++++-------------
1 file changed, 42 insertions(+), 42 deletions(-)
diff --git a/test_plans/dcf_lifecycle_test_plan.rst b/test_plans/dcf_lifecycle_test_plan.rst
index 53837142..d1b19fe1 100644
--- a/test_plans/dcf_lifecycle_test_plan.rst
+++ b/test_plans/dcf_lifecycle_test_plan.rst
@@ -176,7 +176,7 @@ Set a VF as trust ::
Launch dpdk on the VF, request DCF mode ::
./usertools/dpdk-devbind.py -b vfio-pci 18:01.0 18:01.1
- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf --file-prefix=dcf -- -i
+ ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf,representor=vf[1] --file-prefix=dcf -- -i
Launch another testpmd on the VF1, and start mac forward ::
@@ -187,7 +187,7 @@ Launch another testpmd on the VF1, and start mac forward ::
Set switch rule to VF1 `0000:18:01.1` from DCF ::
- flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions vf id 1 / end
+ flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions represented_port ethdev_port_id 1 / end
Send a scapy packet to VF1 ::
@@ -228,7 +228,7 @@ Set a VF as trust ::
Launch dpdk on the VF, request DCF mode ::
./usertools/dpdk-devbind.py -b vfio-pci 18:01.0 18:01.1
- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf --file-prefix=dcf -- -i
+ ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf,representor=vf[1] --file-prefix=dcf -- -i
Launch another testpmd on the VF1, and start mac forward ::
@@ -239,7 +239,7 @@ Launch another testpmd on the VF1, and start mac forward ::
Set switch rule to VF1 0000:18:01.1 from DCF ::
- flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions vf id 1 / end
+ flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions represented_port ethdev_port_id 1 / end
Send a scapy packet to VF1 ::
@@ -277,7 +277,7 @@ Set a VF as trust ::
Launch dpdk on the VF, request DCF mode ::
./usertools/dpdk-devbind.py -b vfio-pci 18:01.0 18:01.1
- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf --file-prefix=dcf -- -i
+ ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf,representor=vf[1] --file-prefix=dcf -- -i
Launch another testpmd on the VF1, and start mac forward ::
@@ -288,7 +288,7 @@ Launch another testpmd on the VF1, and start mac forward ::
Set switch rule to VF1 0000:18:01.1 from DCF ::
- flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions vf id 1 / end
+ flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions represented_port ethdev_port_id 1 / end
Send a scapy packet to VF1 ::
@@ -353,7 +353,7 @@ Set a VF as trust ::
Launch dpdk on the VF, request DCF mode ::
./usertools/dpdk-devbind.py -b vfio-pci 18:01.0 18:01.1
- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf --file-prefix=dcf -- -i
+ ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf,representor=vf[1-2] --file-prefix=dcf -- -i
Launch another testpmd on the VF1 and VF2, and start mac forward ::
@@ -369,8 +369,8 @@ Launch another testpmd on the VF1 and VF2, and start mac forward ::
Set switch rule to VF1 0000:18:01.1 from DCF ::
- flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions vf id 1 / end
- flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.4 dst is 192.168.0.5 / end actions vf id 1 / end
+ flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions represented_port ethdev_port_id 1 / end
+ flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.4 dst is 192.168.0.5 / end actions represented_port ethdev_port_id 1 / end
Send a scapy packet to VF1 ::
@@ -421,9 +421,9 @@ Set a VF as trust ::
Launch dpdk on the VF, request DCF mode ::
./usertools/dpdk-devbind.py -b vfio-pci 18:01.0 18:01.1 18:01.2
- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf --file-prefix=dcf -- -i
+ ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 6-10 -n 4 -a 18:01.0,cap=dcf,representor=vf[1-2] --file-prefix=dcf -- -i
-Launch another testpmd on the VF1, and start mac forward ::
+Launch another testpmd on the VF1 and VF2, and start mac forward ::
./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 11-14 -n 4 -a 18:01.1 -a 18:01.2 --file-prefix=vf -- -i
set verbose 1
@@ -432,7 +432,7 @@ Launch another testpmd on the VF1, and start mac forward ::
Set switch rule to VF1 0000:18:01.1 and VF2 0000:18:01.2 from DCF ::
- flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions vf id 1 / end
+ flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 / end actions represented_port ethdev_port_id 1 / end
Send a scapy packet to VF1 and VF2 ::
@@ -1112,7 +1112,7 @@ The common steps launch two testpmds and kill DCF process, then relaunch two tes
..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
- For <DUT port pci device id>, you can use "0000:3b:01.0,cap=dcf --file-prefix=dcf" for this test plan.
+ For <DUT port pci device id>, you can use "0000:3b:01.0,cap=dcf,representor=vf[1] --file-prefix=dcf" for this test plan.
2. Launch another ``testpmd`` application on the VF1 of DUT as follows::
@@ -1134,7 +1134,7 @@ The common steps launch two testpmds and kill DCF process, then relaunch two tes
5. Validate a switch rule to VF1 in DCF testpmd::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1142,7 +1142,7 @@ The common steps launch two testpmds and kill DCF process, then relaunch two tes
6. Create a switch rule to VF1 in DCF testpmd and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1191,7 +1191,7 @@ Test Steps
..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
- For <DUT port pci device id>, you can use "0000:3b:01.0,cap=dcf --file-prefix=dcf" for this test plan.
+ For <DUT port pci device id>, you can use "0000:3b:01.0,cap=dcf,representor=vf[1] --file-prefix=dcf" for this test plan.
3. Send a matched packet in scapy to VF1, DCF flow rule is still valid and check the VF1 of DUT can receive the packet.
@@ -1216,7 +1216,7 @@ the VF1 of DUT::
5. Validate a switch rule to VF1 in DCF testpmd::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1224,7 +1224,7 @@ the VF1 of DUT::
6. Create a switch rule to VF1 in DCF testpmd and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1270,7 +1270,7 @@ Test Steps
3. Validate a switch rule to VF1 in DCF testpmd::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1278,7 +1278,7 @@ Test Steps
4. Create a switch rule to VF1 in DCF testpmd and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1326,7 +1326,7 @@ Test Steps
3. Validate a switch rule to VF1 in DCF testpmd::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1334,7 +1334,7 @@ Test Steps
4. Create a switch rule to VF1 in DCF testpmd and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1380,7 +1380,7 @@ Test Steps
3. Validate a switch rule to VF1 in DCF testpmd::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1388,7 +1388,7 @@ Test Steps
4. Create a switch rule to VF1 in DCF testpmd and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1434,7 +1434,7 @@ Test Steps
3. Validate a switch rule to VF1 in DCF testpmd::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1442,7 +1442,7 @@ Test Steps
4. Create a switch rule to VF1 in DCF testpmd and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1478,7 +1478,7 @@ The common steps launch one testpmd and kill DCF process, then relaunch one test
..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
- For <DUT port pci device id>, you can use"-a 3b:01.0,cap=dcf -a 3b:01.1 --file-prefix=dcf" for this test plan.
+ For <DUT port pci device id>, you can use"-a 3b:01.0,cap=dcf,representor=vf[1] -a 3b:01.1 --file-prefix=dcf" for this test plan.
2. Set verbose::
@@ -1491,7 +1491,7 @@ The common steps launch one testpmd and kill DCF process, then relaunch one test
4. Validate a switch rule to VF1::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1499,7 +1499,7 @@ The common steps launch one testpmd and kill DCF process, then relaunch one test
5. Create a switch rule to VF1 and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1542,7 +1542,7 @@ Test Steps
..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
- For <DUT port pci device id>, you can use"-a 3b:01.0,cap=dcf -a 3b:01.1 --file-prefix=dcf" for this test plan.
+ For <DUT port pci device id>, you can use"-a 3b:01.0,cap=dcf,representor=vf[1] -a 3b:01.1 --file-prefix=dcf" for this test plan.
3. Set verbose::
@@ -1574,7 +1574,7 @@ DUT::
7. Validate a switch rule to VF1::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1582,7 +1582,7 @@ DUT::
8. Create a switch rule to VF1 and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1628,7 +1628,7 @@ Test Steps
3. Validate a switch rule to VF1::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1636,7 +1636,7 @@ Test Steps
4. Create a switch rule to VF1 and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1676,7 +1676,7 @@ Test Steps
testpmd> stop
testpmd> port stop 0
testpmd> port detach 0
- testpmd> port attach 3b:01.0,cap=dcf
+ testpmd> port attach 3b:01.0,cap=dcf,representor=vf[1]
testpmd> port reset 0
testpmd> port start 0
testpmd> start
@@ -1684,7 +1684,7 @@ Test Steps
3. Validate a switch rule to VF1::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1692,7 +1692,7 @@ Test Steps
4. Create a switch rule to VF1 and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1738,7 +1738,7 @@ Test Steps
3. Validate a switch rule to VF1::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1746,7 +1746,7 @@ Test Steps
4. Create a switch rule to VF1 and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1769,7 +1769,7 @@ DUT::
testpmd> port 1/queue 0: received 1 packets
src=00:11:22:33:44:55 - dst=C6:44:32:0A:EC:E1 - type=0x0800 - length=98 - nb_segs=1 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN L4_NONFRAG - sw ptype: L2_ETHER L3_IPV4 - l2_len=14 - l3_len=20 - Receive queue=0x0
- ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
+ ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
Test Case 10: one_testpmd_dcf_reset_mac
---------------------------------------
@@ -1792,7 +1792,7 @@ Test Steps
3. Validate a switch rule to VF1::
- testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
@@ -1800,7 +1800,7 @@ Test Steps
4. Create a switch rule to VF1 and list rules::
- testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions vf id 1 / end
+ testpmd> flow create 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
Get the message::
--
2.25.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* [DTS][PATCH V1 2/3] test_plans/dcf_lifecycle: remove redundant white space
2022-11-30 3:53 [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 1/3] test_plans/dcf_lifecycle: update test plan to support represented port action from deprecated vf action Ke Xu
@ 2022-11-30 3:53 ` Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 3/3] tests/dcf_lifecycle: update test plan to support represented port action from deprecated vf action Ke Xu
2022-12-13 6:05 ` [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Tu, Lijuan
3 siblings, 0 replies; 5+ messages in thread
From: Ke Xu @ 2022-11-30 3:53 UTC (permalink / raw)
To: dts; +Cc: lijuan.tu, Ke Xu, Jin Ling
Signed-off-by: Jin Ling <jin.ling@intel.com>
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
test_plans/dcf_lifecycle_test_plan.rst | 112 ++++++++++++-------------
1 file changed, 55 insertions(+), 57 deletions(-)
diff --git a/test_plans/dcf_lifecycle_test_plan.rst b/test_plans/dcf_lifecycle_test_plan.rst
index d1b19fe1..8475698a 100644
--- a/test_plans/dcf_lifecycle_test_plan.rst
+++ b/test_plans/dcf_lifecycle_test_plan.rst
@@ -1046,9 +1046,9 @@ ICE DCF enable device reset API
Description
===========
-DCF PMD need to support rte_eth_dev_reset.The reason is that when a DCF instance be killed, all the flow rules still exist in hardware. when DCF gets to reconnect,
-It has already lost the flow context, and if the application wants to create new rules, they may fail because FW reports that the rules already exist.The current
-workaround assumes that the user can turn off / turn on VF trust mode, so kernel PF will reset DCF by removing all old rules.The rte_eth_dev_reset API provides
+DCF PMD need to support rte_eth_dev_reset.The reason is that when a DCF instance be killed, all the flow rules still exist in hardware. when DCF gets to reconnect,
+It has already lost the flow context, and if the application wants to create new rules, they may fail because FW reports that the rules already exist.The current
+workaround assumes that the user can turn off / turn on VF trust mode, so kernel PF will reset DCF by removing all old rules.The rte_eth_dev_reset API provides
a more elegant way for the application to reset DCF through the command "port reset all" when reconnecting.
Prerequisites
@@ -1070,7 +1070,7 @@ General Set Up
# CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib --default-library=static <dpdk build dir>
# ninja -C <dpdk build dir> -j 110
-2. Get the pci device id and interface of DUT and tester.
+2. Get the pci device id and interface of DUT and tester.
For example, 0000:3b:00.0 and 0000:af:00.0 is pci device id,
ens785f0 and ens260f0 is interface::
@@ -1097,7 +1097,7 @@ General Set Up
6. Bind the DUT port to dpdk::
<dpdk dir># ./usertools/dpdk-devbind.py -b vfio-pci <DUT port pci device id>
-
+
Test case
=========
@@ -1107,26 +1107,26 @@ The common steps launch two testpmds and kill DCF process, then relaunch two tes
1. Launch the userland ``testpmd`` application on DUT as follows::
- <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
+ <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
-..note::
+..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
For <DUT port pci device id>, you can use "0000:3b:01.0,cap=dcf,representor=vf[1] --file-prefix=dcf" for this test plan.
-
+
2. Launch another ``testpmd`` application on the VF1 of DUT as follows::
- <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
+ <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
-..note::
+..note::
For <EAL options>, you can use "-c 0x18 -n 4", you can also refer to testpmd doc for other setings.
- For this test plan, you can use "0000:3b:01.1 --file-prefix=vf" for this test plan.
+ For this test plan, you can use "0000:3b:01.1 --file-prefix=vf" for this test plan.
3. Set verbose in VF testpmd::
-
+
testpmd> set verbose 1
-
+
4. Set fwd engine and start in VF testpmd::
testpmd> set fwd mac
@@ -1151,7 +1151,7 @@ The common steps launch two testpmds and kill DCF process, then relaunch two tes
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1181,14 +1181,14 @@ Test Steps
~~~~~~~~~~
1. Check the process ID and kill DCF process::
- # ps -ef |grep testpmd
+ # ps -ef |grep testpmd
# kill -9 #####
2. Relaunch the userland ``testpmd`` application on DUT as follows::
- <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
+ <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
-..note::
+..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
For <DUT port pci device id>, you can use "0000:3b:01.0,cap=dcf,representor=vf[1] --file-prefix=dcf" for this test plan.
@@ -1233,7 +1233,7 @@ the VF1 of DUT::
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1260,7 +1260,7 @@ Test Steps
# echo 1 > /sys/bus/pci/devices/0000:3b:01.0/reset
2. Reset port in DCF testpmd::
-
+
testpmd> stop
testpmd> port stop all
testpmd> port reset all
@@ -1287,7 +1287,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1314,8 +1314,8 @@ Test Steps
# echo 1 > /sys/bus/pci/devices/0000:3b:01.0/reset
2. Detach and reset port in DCF testpmd::
-
- testpmd> stop
+
+ testpmd> stop
testpmd> port stop 0
testpmd> port detach 0
testpmd> port attach 3b:01.0,cap=dcf
@@ -1343,7 +1343,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1357,7 +1357,7 @@ the VF1 of DUT::
testpmd> port 0/queue 0: received 1 packets
src=00:11:22:33:44:55 - dst=C6:44:32:0A:EC:E1 - type=0x0800 - length=98 - nb_segs=1 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN L4_NONFRAG - sw ptype: L2_ETHER L3_IPV4 - l2_len=14 - l3_len=20 - Receive queue=0x0
- ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
+ ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
Test Case 4: two_testpmd_dcf_reset_mtu
--------------------------------------
@@ -1370,14 +1370,14 @@ Test Steps
# ifconfig ens785f0 mtu 3000
2. Reset port in DCF testpmd::
-
+
testpmd> stop
testpmd> port stop all
testpmd> port reset all
testpmd> port start all
testpmd> start
testpmd> flow list 0
-
+
3. Validate a switch rule to VF1 in DCF testpmd::
testpmd> flow validate 0 priority 0 ingress pattern eth / ipv4 src is <ipv4 src> dst is <ipv4 dst> / end actions represented_port ethdev_port_id 1 / end
@@ -1397,7 +1397,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1412,7 +1412,7 @@ the VF1 of DUT::
testpmd> port 0/queue 0: received 1 packets
src=00:11:22:33:44:55 - dst=C6:44:32:0A:EC:E1 - type=0x0800 - length=98 - nb_segs=1 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN L4_NONFRAG - sw ptype: L2_ETHER L3_IPV4 - l2_len=14 - l3_len=20 - Receive queue=0x0
ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
-
+
Test Case 5: two_testpmd_dcf_reset_mac
--------------------------------------
The test case resets DCF by resetting mac addr, and DCF should clean up all old rules.
@@ -1424,7 +1424,7 @@ Test Steps
# ip link set ens785f0 vf 0 mac 00:01:02:03:04:05
2. Reset port in DCF testpmd::
-
+
testpmd> stop
testpmd> port stop all
testpmd> port reset all
@@ -1451,7 +1451,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1473,17 +1473,17 @@ The common steps launch one testpmd and kill DCF process, then relaunch one test
1. Launch the userland ``testpmd`` application on DUT as follows::
- <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
+ <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
-..note::
+..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
For <DUT port pci device id>, you can use"-a 3b:01.0,cap=dcf,representor=vf[1] -a 3b:01.1 --file-prefix=dcf" for this test plan.
2. Set verbose::
-
+
testpmd> set verbose 1
-
+
3. Set fwd engine and start::
testpmd> set fwd mac
@@ -1508,7 +1508,7 @@ The common steps launch one testpmd and kill DCF process, then relaunch one test
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1532,22 +1532,22 @@ Test Steps
~~~~~~~~~~
1. Check the process ID and kill DCF process::
- # ps -ef |grep testpmd
+ # ps -ef |grep testpmd
# kill -9 #####
2. Relaunch the userland ``testpmd`` application on DUT as follows::
- <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
+ <dpdk build dir>/app/dpdk-testpmd <EAL options> -a <DUT port pci device id> -- -i
-..note::
+..note::
For <EAL options>, you can use "-c 0x6 -n 4", you can also refer to testpmd doc for other setings.
For <DUT port pci device id>, you can use"-a 3b:01.0,cap=dcf,representor=vf[1] -a 3b:01.1 --file-prefix=dcf" for this test plan.
3. Set verbose::
-
+
testpmd> set verbose 1
-
+
4. Set fwd engine and start::
testpmd> set fwd mac
@@ -1562,10 +1562,10 @@ Tester::
DUT::
- testpmd>
+ testpmd>
6. Reset port in testpmd::
-
+
testpmd> stop
testpmd> port stop all
testpmd> port reset all
@@ -1591,7 +1591,7 @@ DUT::
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1605,7 +1605,7 @@ DUT::
testpmd> port 1/queue 0: received 1 packets
src=00:11:22:33:44:55 - dst=C6:44:32:0A:EC:E1 - type=0x0800 - length=98 - nb_segs=1 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN L4_NONFRAG - sw ptype: L2_ETHER L3_IPV4 - l2_len=14 - l3_len=20 - Receive queue=0x0
- ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
+ ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
Test Case 7: one_testpmd_dcf_reset_device
-----------------------------------------
@@ -1618,7 +1618,7 @@ Test Steps
# echo 1 > /sys/bus/pci/devices/0000:3b:01.0/reset
2. Reset port in testpmd::
-
+
testpmd> stop
testpmd> port stop all
testpmd> port reset all
@@ -1645,7 +1645,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1672,8 +1672,8 @@ Test Steps
# echo 1 > /sys/bus/pci/devices/0000:3b:01.0/reset
2. Detach and reset port in DCF testpmd::
-
- testpmd> stop
+
+ testpmd> stop
testpmd> port stop 0
testpmd> port detach 0
testpmd> port attach 3b:01.0,cap=dcf,representor=vf[1]
@@ -1701,7 +1701,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1715,7 +1715,7 @@ DUT::
testpmd> port 1/queue 0: received 1 packets
src=00:11:22:33:44:55 - dst=C6:44:32:0A:EC:E1 - type=0x0800 - length=98 - nb_segs=1 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN L4_NONFRAG - sw ptype: L2_ETHER L3_IPV4 - l2_len=14 - l3_len=20 - Receive queue=0x0
- ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
+ ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
Test Case 9: one_testpmd_dcf_reset_mtu
--------------------------------------
@@ -1728,13 +1728,13 @@ Test Steps
# ifconfig ens785f0 mtu 3000
2. Reset port in DCF testpmd::
-
+
testpmd> stop
testpmd> port stop all
testpmd> port reset all
testpmd> port start all
testpmd> start
- testpmd> flow list 0
+ testpmd> flow list 0
3. Validate a switch rule to VF1::
@@ -1755,7 +1755,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1782,7 +1782,7 @@ Test Steps
# ip link set ens785f0 vf 0 mac 00:01:02:03:04:05
2. Reset port in DCF testpmd::
-
+
testpmd> stop
testpmd> port stop all
testpmd> port reset all
@@ -1809,7 +1809,7 @@ Test Steps
Check the flow list::
testpmd> flow list 0
-
+
ID Group Prio Attr Rule
0 0 0 i-- ETH IPV4 => VF
@@ -1824,5 +1824,3 @@ DUT::
testpmd> port 1/queue 0: received 1 packets
src=00:11:22:33:44:55 - dst=C6:44:32:0A:EC:E1 - type=0x0800 - length=98 - nb_segs=1 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN L4_NONFRAG - sw ptype: L2_ETHER L3_IPV4 - l2_len=14 - l3_len=20 - Receive queue=0x0
ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
-
-
--
2.25.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* [DTS][PATCH V1 3/3] tests/dcf_lifecycle: update test plan to support represented port action from deprecated vf action
2022-11-30 3:53 [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 1/3] test_plans/dcf_lifecycle: update test plan to support represented port action from deprecated vf action Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 2/3] test_plans/dcf_lifecycle: remove redundant white space Ke Xu
@ 2022-11-30 3:53 ` Ke Xu
2022-12-13 6:05 ` [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Tu, Lijuan
3 siblings, 0 replies; 5+ messages in thread
From: Ke Xu @ 2022-11-30 3:53 UTC (permalink / raw)
To: dts; +Cc: lijuan.tu, Ke Xu, Jin Ling
A new API is introduced to replace the VF actions in DPDK 22.11. To support This
new API, several modifications are made.
New field is added in setup for applying representor to the case.
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.
Signed-off-by: Jin Ling <jin.ling@intel.com>
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
tests/TestSuite_dcf_lifecycle.py | 24 +++++++++++++-----------
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/tests/TestSuite_dcf_lifecycle.py b/tests/TestSuite_dcf_lifecycle.py
index 1c97412c..cd7e1824 100644
--- a/tests/TestSuite_dcf_lifecycle.py
+++ b/tests/TestSuite_dcf_lifecycle.py
@@ -239,11 +239,13 @@ class TestDcfLifeCycle(TestCase):
)
allowlist = {
"pf1_vf0_dcf": f"-a {pf1_vf0},cap=dcf",
+ "pf1_vf0_dcf_repre_vf1": f"-a {pf1_vf0},cap=dcf,representor=vf[1]",
"pf1_vf1_dcf": f"-a {pf1_vf1},cap=dcf",
"pf1_vf0_pf2_vf0_dcf": f"-a {pf1_vf0},cap=dcf -a {pf2_vf0},cap=dcf",
"pf1_vf1_vf2": f"-a {pf1_vf1} -a {pf1_vf2}",
"pf1_vf1": f"-a {pf1_vf1}",
"pf2_vf0_dcf": f"-a {pf2_vf0},cap=dcf",
+ "pf2_vf0_dcf_repre_vf1": f"-a {pf2_vf0},cap=dcf,representor=vf[1]",
"pf1_vf0": f"-a {pf1_vf0}",
"pf1_vf0_dcf_vf1": f"-a {pf1_vf0},cap=dcf -a {pf1_vf1}",
}
@@ -278,11 +280,11 @@ class TestDcfLifeCycle(TestCase):
"{port} "
"priority 0 "
"ingress pattern eth / ipv4 src is {ip_src} dst is {ip_dst} / end "
- "actions vf id {vf_id} / end"
+ "actions represented_port ethdev_port_id {vf_id} / end"
).format(
**{
"port": dut_port_id,
- "vf_id": 1,
+ "vf_id": dut_port_id + 1,
"ip_src": self.get_ip_layer()["ipv4"]["src"],
"ip_dst": self.get_ip_layer()["ipv4"]["dst"],
}
@@ -664,7 +666,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_pmd2_traffic("close_vf_dcf_testpmd")
@@ -684,7 +686,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_pmd2_traffic("vf_set_trust_off")
@@ -704,7 +706,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_pmd2_traffic(
@@ -760,7 +762,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_pmd2_traffic("vf_set_mac_addr", flag=True)
@@ -1642,7 +1644,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_traffic(
@@ -1668,7 +1670,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_traffic("vf_dcf_reset_device")
@@ -1690,7 +1692,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_traffic("vf_dcf_reset_port_detach")
@@ -1712,7 +1714,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_traffic("vf_dcf_reset_mtu")
@@ -1734,7 +1736,7 @@ class TestDcfLifeCycle(TestCase):
except_content = None
try:
self.vf_set_trust()
- pmd_opts = [["pf1_vf0_dcf", "dcf"], ["pf1_vf1", "vf"]]
+ pmd_opts = [["pf1_vf0_dcf_repre_vf1", "dcf"], ["pf1_vf1", "vf"]]
self.run_test_pre(pmd_opts)
self.vf_dcf_testpmd_set_flow_rule()
self.check_vf_traffic("vf_dcf_set_mac_addr")
--
2.25.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle
2022-11-30 3:53 [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Ke Xu
` (2 preceding siblings ...)
2022-11-30 3:53 ` [DTS][PATCH V1 3/3] tests/dcf_lifecycle: update test plan to support represented port action from deprecated vf action Ke Xu
@ 2022-12-13 6:05 ` Tu, Lijuan
3 siblings, 0 replies; 5+ messages in thread
From: Tu, Lijuan @ 2022-12-13 6:05 UTC (permalink / raw)
To: Xu, Ke1, dts
> -----Original Message-----
> From: Xu, Ke1 <ke1.xu@intel.com>
> Sent: Wednesday, November 30, 2022 11:53 AM
> To: dts@dpdk.org
> Cc: Tu, Lijuan <lijuan.tu@intel.com>; Xu, Ke1 <ke1.xu@intel.com>
> Subject: [DTS][PATCH V1 0/3] update test plans and tests to support
> represented port action and port representor action from deprecated vf
> action in dcf_lifecycle
>
> 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.
>
> New fields are added in setup for applying representor to the case.
>
> 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.
>
> Duplicated whitespaces are removed and extra whitespaces are added to
> formate the document.
>
> Jin Ling (3):
> test_plans/dcf_lifecycle: update test plan to support represented port
> action from deprecated vf action
> test_plans/dcf_lifecycle: remove redundant white space
> tests/dcf_lifecycle: update test plan to support represented port
> action from deprecated vf action
Applied, thanks
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-12-13 6:06 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-30 3:53 [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 1/3] test_plans/dcf_lifecycle: update test plan to support represented port action from deprecated vf action Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 2/3] test_plans/dcf_lifecycle: remove redundant white space Ke Xu
2022-11-30 3:53 ` [DTS][PATCH V1 3/3] tests/dcf_lifecycle: update test plan to support represented port action from deprecated vf action Ke Xu
2022-12-13 6:05 ` [DTS][PATCH V1 0/3] update test plans and tests to support represented port action and port representor action from deprecated vf action in dcf_lifecycle Tu, Lijuan
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).