From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 9E413A00E6 for ; Wed, 17 Apr 2019 09:33:24 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 958991B42C; Wed, 17 Apr 2019 09:33:24 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 1D77F1B3BB for ; Wed, 17 Apr 2019 09:33:22 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2019 00:33:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,361,1549958400"; d="scan'208";a="292243906" Received: from xuyanjie.sh.intel.com ([10.67.111.13]) by orsmga004.jf.intel.com with ESMTP; 17 Apr 2019 00:33:21 -0700 From: xuyanjie To: dts@dpdk.org Cc: xuyanjie Date: Wed, 17 Apr 2019 09:19:37 -0400 Message-Id: <1555507177-171382-1-git-send-email-yanjie.xu@intel.com> X-Mailer: git-send-email 2.7.4 Subject: [dts] [PATCH] blacklist clarify hardware requirement X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 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" Signed-off-by: xuyanjie diff --git a/test_plans/blacklist_test_plan.rst b/test_plans/blacklist_test_plan.rst index 02b3c2f..add44bb 100644 --- a/test_plans/blacklist_test_plan.rst +++ b/test_plans/blacklist_test_plan.rst @@ -34,13 +34,17 @@ Port Blacklist Tests ==================== +Hardwares +============= +i40e and ixgbe NIC supported, number of NIC>=2 + Prerequisites ============= Board with at least 2 DPDK supported NICs attached. If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When -using vfio, use the following commands to load the vfio driver and bind it +using vfio, use the following commands to to load the vfio driver and bind it to the device under test:: modprobe vfio @@ -53,7 +57,7 @@ Test Case: Testpmd with no blacklisted device Run testpmd in interactive mode and ensure that at least 2 ports are bound and available:: - build/testpmd -c 3 -- -i + ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x6 -n 4 -- -i .... EAL: unbind kernel driver /sys/bus/pci/devices/0000:01:00.0/driver/unbind EAL: Core 1 is ready (tid=357fc700) @@ -91,7 +95,7 @@ Test Case: Testpmd with one port blacklisted Select first available port to be blacklisted and specify it with -b option. For the example above:: - build/testpmd -c 3 -b 0000:01:00.0 -- -i + ./x86_64-native-linuxapp-gcc/app/testpmd -c 3 -b 0000:01:00.0 -- -i Check that corresponding device is skipped for binding, and only 3 ports are available now::: @@ -126,7 +130,7 @@ Test Case: Testpmd with all but one port blacklisted Blacklist all devices except the last one. For the example above::: - build/testpmd -c 3 -b 0000:01:00.0 -b 0000:01:00.0 -b 0000:02:00.0 -- -i + ./x86_64-native-linuxapp-gcc/app/testpmd -c 3 -b 0000:01:00.0 -b 0000:01:00.0 -b 0000:02:00.0 -- -i Check that 3 corresponding device is skipped for binding, and only 1 ports is available now::: -- 2.7.4