From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id ACDECA04AF; Tue, 8 Feb 2022 12:21:19 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9DEAE41141; Tue, 8 Feb 2022 12:21:19 +0100 (CET) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id CB71A41141 for ; Tue, 8 Feb 2022 12:21:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1644319279; x=1675855279; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=/cG/N6TIXHF7ZHrEQLaAsNAqzlQjXiaPX2lXEDWQxvE=; b=gpwJ9+XAo8zuJsDc0deRS/oNNA/bwBdeZwuDIre6UQVvvvHsdQ8RlAcW ap6SnTG5DBUu0iTPjY3SL23lYfb1fDb3JHctDghh7/L65+FXRoPXRAqJf EG/fUTyNg8vdKRcw5+cugSb3VkruM5e8Xm5WdOkmjZtw80cNFnkd9qLQ2 YWEF5hPej9xHnDaYlOUKrY0Tu/oMHTZtQhNHsQ0p4CDKlX3g/BzKVwoUh NE2Kvw/34VcQ2nEqV6j5wSZeC0340X6Iw8EgiexIbinX8444E4n6REHdu 8WzriSONyzX+AThWLEBViZEZnSML6XhLrpcfi2of5gy+zYIetDrLUzdN4 g==; X-IronPort-AV: E=McAfee;i="6200,9189,10251"; a="248691793" X-IronPort-AV: E=Sophos;i="5.88,352,1635231600"; d="scan'208";a="248691793" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Feb 2022 03:21:18 -0800 X-IronPort-AV: E=Sophos;i="5.88,352,1635231600"; d="scan'208";a="540557538" Received: from unknown (HELO localhost.localdomain.sh.intel.com) ([10.239.251.86]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Feb 2022 03:21:17 -0800 From: Weiyuan Li To: dts@dpdk.org, xueqin.lin@intel.com Cc: Weiyuan Li Subject: [dts][PATCH V1 2/2] test_plans/generic_flow_api_test_plan: remove dpdk code modification. Date: Wed, 9 Feb 2022 22:21:06 +0800 Message-Id: <20220209142106.6753-2-weiyuanx.li@intel.com> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20220209142106.6753-1-weiyuanx.li@intel.com> References: <20220209142106.6753-1-weiyuanx.li@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sync modify the test plan remove dpdk code modification. Signed-off-by: Weiyuan Li --- test_plans/generic_flow_api_test_plan.rst | 28 +++++++++-------------- 1 file changed, 11 insertions(+), 17 deletions(-) diff --git a/test_plans/generic_flow_api_test_plan.rst b/test_plans/generic_flow_api_test_plan.rst index c4c0301e..27ebc72f 100644 --- a/test_plans/generic_flow_api_test_plan.rst +++ b/test_plans/generic_flow_api_test_plan.rst @@ -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. -- 2.27.0