From patchwork Wed Sep 28 03:18:23 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ke Xu X-Patchwork-Id: 116980 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 76171A00C2; Wed, 28 Sep 2022 05:24:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6F28F427F1; Wed, 28 Sep 2022 05:24:23 +0200 (CEST) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mails.dpdk.org (Postfix) with ESMTP id 5DAA340E25 for ; Wed, 28 Sep 2022 05:24:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1664335462; x=1695871462; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=n0APxYUpd62YIatGRIvZXbky2tTbBfmGZTW8Hco49Fg=; b=Rc2PDT4w7Qeowj+QhnrFyuG6tR4ZCiEzLjEUH8DGlrcbOOOi5Fnrkd2p EV8bTGQhMmMyNW1ezXUvDsRMP4pZR8f7KkCMfHx8QH3qS3bscScJuloNz i8slt28f5y2PuHErK65Bnsku85fGg5Z+EvbrgA3RQQqKEbjc4ZpbZH+UD Jqof2yAPCCQgyPuNOhGYCMB8uIh9i4SbHo6shx0zGQIweYatBHIwIWw7J ytPqsrFKw3AsgO6zmMQ24jekD3dJVRv5BEcrMWW24axBeGkNEpazdz1zV ah3sF11O3syScuvoE6ZZB6yiP3y6fHhEAcQ/cgB0uL4dj6KhF7wLt0oi3 w==; X-IronPort-AV: E=McAfee;i="6500,9779,10483"; a="301469918" X-IronPort-AV: E=Sophos;i="5.93,350,1654585200"; d="scan'208";a="301469918" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Sep 2022 20:24:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10483"; a="710802749" X-IronPort-AV: E=Sophos;i="5.93,350,1654585200"; d="scan'208";a="710802749" Received: from unknown (HELO DPDK-XUKE-LAB.sh.intel.com) ([10.67.116.226]) by FMSMGA003.fm.intel.com with ESMTP; 27 Sep 2022 20:24:19 -0700 From: Ke Xu To: dts@dpdk.org Cc: lijuan.tu@intel.com, jin.ling@intel.com, zhiminx.huang@intel.com, weiyuanx.li@intel.com, qi.fu@intel.com, Ke Xu Subject: [DTS][PATCH V1 03/21] test_plans/ice_limit_value_test: update test plan to support represented port action from deprecated vf action Date: Wed, 28 Sep 2022 03:18:23 +0000 Message-Id: <20220928031836.770004-4-ke1.xu@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220928031836.770004-1-ke1.xu@intel.com> References: <20220928031836.770004-1-ke1.xu@intel.com> MIME-Version: 1.0 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 Signed-off-by: Jin Ling Reviewed-by: Ke Xu --- test_plans/ice_limit_value_test_test_plan.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/test_plans/ice_limit_value_test_test_plan.rst b/test_plans/ice_limit_value_test_test_plan.rst index 70311efd..4b76dc17 100644 --- a/test_plans/ice_limit_value_test_test_plan.rst +++ b/test_plans/ice_limit_value_test_test_plan.rst @@ -500,8 +500,8 @@ Prerequisites 8. Launch dpdk on VF0 and VF1, and VF0 request DCF mode:: - ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0xf -n 4 -a 0000:18:01.0,cap=dcf -a 0000:18:01.1 -- -i - testpmd> set portlist 1 + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0xf -n 4 -a 0000:18:01.0,cap=dcf,representor=vf[1] -a 0000:18:01.1 -- -i + testpmd> set portlist 2 testpmd> set fwd rxonly testpmd> set verbose 1 testpmd> start @@ -531,17 +531,17 @@ increased, so we can create a total of 32500 switch filter rules on a DCF. 1. create 32500 rules with the same pattern, but different input set:: - testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.0.0 / end actions vf id 1 / end - testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.0.1 / end actions vf id 1 / end + testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.0.0 / end actions represented_port ethdev_port_id 1 / end + testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.0.1 / end actions represented_port ethdev_port_id 1 / end ...... - testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.127.114 / end actions vf id 1 / end + testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.127.114 / end actions represented_port ethdev_port_id 1 / end testpmd> flow list 0 check the rules exist in the list. 2. create one more rule:: - testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.127.178 / end actions vf id 1 / end + testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.127.178 / end actions represented_port ethdev_port_id 1 / end check the rule can not be created successfully, and testpmd provide a friendly output, showing::