[V1,2/2] test_plans/generic_flow_api_test_plan: remove dpdk code modification.
Checks
Commit Message
Sync modify the test plan remove dpdk code modification.
Signed-off-by: Weiyuan Li <weiyuanx.li@intel.com>
---
test_plans/generic_flow_api_test_plan.rst | 28 +++++++++--------------
1 file changed, 11 insertions(+), 17 deletions(-)
Comments
> - ./dpdk-testpmd -l
> 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,37,38,39,40,41,42,43,44,45,46,47,48,
> 49,50,51,52,53 -n 4 -- -i --disable-rss --rxq=128 --txq=128 --portmask=0x3 --nb-
> cores=4 --total-num-mbufs=263168
> + ./dpdk-testpmd -l
> 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,37,38,39,40,41,42,43,44,45,46,47,48,
> 49,50,51,52,53 -n 4 -- -i --disable-rss --rxq=64 --txq=64 --portmask=0x3 --nb-
> cores=4 --total-num-mbufs=263168
''./dpdk-testpmd -l 1-5 is more reasonable, as only use 4 cores for pmd, and 1 core for eal, so totaling 5 cores are used.
List so many cores is not human friendly.
thanks
@@ -2213,20 +2213,14 @@ the packet are not received on the queue 2::
testpmd> stop
-Test Case: 128 queues
+Test Case: 64 queues
========================
-This case is designed for NIC(niantic). Since NIC(niantic) has 128 transmit
-queues, it should be supports 128 kinds of filter if Hardware have enough
-cores.
-DPDK enable 64 queues in ixgbe driver by default. Enlarge queue number to 128
-for 128 queues test::
-
- sed -i -e 's/#define IXGBE_NONE_MODE_TX_NB_QUEUES 64$/#define IXGBE_NONE_MODE_TX_NB_QUEUES 128/' drivers/net/ixgbe/ixgbe_ethdev.h
+This case is designed for NIC(niantic). Default use 64 queues for test
Launch the app ``testpmd`` with the following arguments::
- ./dpdk-testpmd -l 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53 -n 4 -- -i --disable-rss --rxq=128 --txq=128 --portmask=0x3 --nb-cores=4 --total-num-mbufs=263168
+ ./dpdk-testpmd -l 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53 -n 4 -- -i --disable-rss --rxq=64 --txq=64 --portmask=0x3 --nb-cores=4 --total-num-mbufs=263168
testpmd>set stat_qmap rx 0 0 0
testpmd>set stat_qmap rx 1 0 0
@@ -2235,17 +2229,17 @@ Launch the app ``testpmd`` with the following arguments::
testpmd>vlan set filter off 0
testpmd>vlan set filter off 1
-Create the 5-tuple Filters with different queues (64,127) on port 0 for
+Create the 5-tuple Filters with different queues (32,63) on port 0 for
niantic::
- testpmd> set stat_qmap rx 0 64 1
- testpmd> flow create 0 ingress pattern eth / ipv4 dst is 2.2.2.5 src is 2.2.2.4 / tcp dst is 1 src is 1 / end actions queue index 64 / end
- testpmd> set stat_qmap rx 0 127 2
- testpmd> flow create 0 ingress pattern eth / ipv4 dst is 2.2.2.5 src is 2.2.2.4 / tcp dst is 2 src is 1 / end actions queue index 127 / end
+ testpmd> set stat_qmap rx 0 32 1
+ testpmd> flow create 0 ingress pattern eth / ipv4 dst is 2.2.2.5 src is 2.2.2.4 / tcp dst is 1 src is 1 / end actions queue index 32 / end
+ testpmd> set stat_qmap rx 0 63 2
+ testpmd> flow create 0 ingress pattern eth / ipv4 dst is 2.2.2.5 src is 2.2.2.4 / tcp dst is 2 src is 1 / end actions queue index 63 / end
Send packets(`dst_ip` = 2.2.2.5 `src_ip` = 2.2.2.4 `dst_port` = 1 `src_port` =
1 `protocol` = tcp) and (`dst_ip` = 2.2.2.5 `src_ip` = 2.2.2.4 `dst_port` = 2
`src_port` = 1 `protocol` = tcp ). Then reading the stats for port 0 after
-sending packets. packets are received on the queue 64 and queue 127 When
-setting 5-tuple Filter with queue(128), it will display failure because the
-number of queues no more than 128.
+sending packets. packets are received on the queue 32 and queue 63 When
+setting 5-tuple Filter with queue(64), it will display failure because the
+number of queues no more than 64.