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 37CCDA0C57; Fri, 5 Nov 2021 03:49:53 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BC0DF4111D; Fri, 5 Nov 2021 03:49:51 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mails.dpdk.org (Postfix) with ESMTP id 98A0B410E9 for ; Fri, 5 Nov 2021 03:49:50 +0100 (CET) X-IronPort-AV: E=McAfee;i="6200,9189,10158"; a="219031023" X-IronPort-AV: E=Sophos;i="5.87,210,1631602800"; d="scan'208";a="219031023" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Nov 2021 19:49:50 -0700 X-IronPort-AV: E=Sophos;i="5.87,210,1631602800"; d="scan'208";a="501790606" Received: from unknown (HELO localhost.localdomain) ([10.240.183.163]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 04 Nov 2021 19:49:48 -0700 From: Yu Jiang To: yuan.peng@intel.com, dts@dpdk.org Cc: Yu Jiang Date: Fri, 5 Nov 2021 10:49:23 +0800 Message-Id: <1636080565-26720-2-git-send-email-yux.jiang@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1636080565-26720-1-git-send-email-yux.jiang@intel.com> References: <1636080565-26720-1-git-send-email-yux.jiang@intel.com> Subject: [dts] [PATCH V2 1/3] test_plans/fdir: move case: fdir for Control levels of FDir match reporting to generic_flow_api 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 Sender: "dts" move plan for case: Control levels of FDir match reporting to generic_flow_api Signed-off-by: Yu Jiang --- test_plans/fdir_test_plan.rst | 134 ------------------------------------------ 1 file changed, 134 deletions(-) diff --git a/test_plans/fdir_test_plan.rst b/test_plans/fdir_test_plan.rst index dee03c3..72ac320 100644 --- a/test_plans/fdir_test_plan.rst +++ b/test_plans/fdir_test_plan.rst @@ -199,140 +199,6 @@ are free to be used is equal to 8192 (8192 * 32B = 256KB).:: ######################################################################## -Test case: Control levels of FDir match reporting -================================================= - -The status of FDir filter matching for each packet can be reported by the -hardware through the RX descriptor of each received packet, and this information -is copied into the packet mbuf, that can be examined by the application. - -There are three different reporting modes, that can be set in testpmd using the -``--pkt-filter-report-hash`` command line argument: - - -Sub-case: ``--pkt-filter-report-hash=none`` mode ------------------------------------------------- - -In this mode FDir reporting mode, matches are never reported. -Start the ``testpmd`` application as follows:: - - ./testpmd -c 0xf -- -i --portmask=0x1 --nb-cores=2 --rxq=2 --txq=2 - --disable-rss --pkt-filter-mode=perfect --pkt-filter-report-hash=none - testpmd> set verbose 1 - testpmd> set fwd rxonly - testpmd> start - -Send the ``p_udp`` packet with Scapy on the traffic generator and check that no -FDir information is printed:: - - testpmd> port 0/queue 0: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - nb_segs=1 - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - -Add a perfect filter to match the ``p_udp`` packet, and send the packet again. -No Dir information is printed, but it can be seen that the packet went to queue -1:: - - testpmd> add_perfect_filter 0 udp src 192.168.0.1 1024 dst 192.168.0.2 1024 - flexbytes 0x800 vlan 0 queue 1 soft 0x14 - testpmd> port 0/queue 1: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - nb_segs=1 - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - - -Sub-case: ``--pkt-filter-report-hash=match`` mode -------------------------------------------------- - -In this mode FDir reporting mode, FDir information is printed for packets that -match a filter. -Start the ``testpmd`` application as follows:: - - ./testpmd -c 0xf -- -i --portmask=0x1 --nb-cores=2 --rxq=2 --txq=2 --disable-rss - --pkt-filter-mode=perfect --pkt-filter-report-hash=match - testpmd> set verbose 1 - testpmd> set fwd rxonly - testpmd> start - -Send the ``p_udp`` packet with Scapy on the traffic generator and check that no -FDir information is printed:: - - testpmd> port 0/queue 0: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - nb_segs=1 - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - -Add a perfect filter to match the ``p_udp`` packet, and send the packet again. -This time, the match is indicated (``PKT_RX_PKT_RX_FDIR``), and its details -(hash, id) printed :: - - testpmd> add_perfect_filter 0 udp src 192.168.0.1 1024 dst 192.168.0.2 1024 - flexbytes 0x800 vlan 0 queue 1 soft 0x14 - testpmd> port 0/queue 1: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - -nb_segs=1 - FDIR hash=0x43c - FDIR id=0x14 - PKT_RX_PKT_RX_FDIR - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - -Update the perfect filter to match the ``p_udp1`` packet, and send the packet again. -This time, the match is indicated (``PKT_RX_PKT_RX_FDIR``), and its details -(hash, id) printed :: - - testpmd> add_perfect_filter 0 udp src 192.168.1.1 1024 dst 192.168.1.2 0 - flexbytes 0x800 vlan 0 queue 1 soft 0x14 - testpmd> port 0/queue 1: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - -nb_segs=1 - FDIR hash=0x43c - FDIR id=0x14 - PKT_RX_PKT_RX_FDIR - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - -Remove the perfect filter match the ``p_udp1`` and ``p_udp`` packets, and send the packet again. -Check that no FDir information is printed:: - - testpmd> port 0/queue 0: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - nb_segs=1 - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - -Sub-case: ``--pkt-filter-report-hash=always`` mode --------------------------------------------------- - -In this mode FDir reporting mode, FDir information is printed for every received -packet. -Start the ``testpmd`` application as follows:: - - ./testpmd -c 0xf -- -i --portmask=0x1 --nb-cores=2 --rxq=2 --txq=2 --disable-rss - --pkt-filter-mode=perfect --pkt-filter-report-hash=always - testpmd> set verbose 1 - testpmd> set fwd rxonly - testpmd> start - -Send the ``p_udp`` packet with Scapy on the traffic generator and check the -output (FDIR id=0x0):: - - testpmd> port 0/queue 0: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - - nb_segs=1 - FDIR hash=0x43c - FDIR id=0x0 - PKT_RX_PKT_RX_FDIR - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - -Add a perfect filter to match the ``p_udp`` packet, and send the packet again. -This time, the filter ID is different, and the packet goes to queue 1 :: - - testpmd> add_perfect_filter 0 udp src 192.168.0.1 1024 dst 192.168.0.2 1024 - flexbytes 0x800 vlan 0 queue 1 soft 0x14 - testpmd> port 0/queue 1: received 1 packets - src=00:1B:21:53:1F:14 - dst=00:1B:21:91:3D:2C - type=0x0800 - length=60 - - nb_segs=1 - FDIR hash=0x43c - FDIR id=0x14 - PKT_RX_PKT_RX_FDIR - PKT_RX_IP_CKSUM - PKT_RX_IPV4_HDR - - Test case: FDir signature matching mode ======================================= -- 2.7.4