From: xuyanjie <yanjie.xu@intel.com>
To: dts@dpdk.org
Cc: xuyanjie <yanjie.xu@intel.com>
Subject: [dts] [PATCH] blacklist clarify hardware requirement
Date: Wed, 17 Apr 2019 09:19:37 -0400 [thread overview]
Message-ID: <1555507177-171382-1-git-send-email-yanjie.xu@intel.com> (raw)
Signed-off-by: xuyanjie <yanjie.xu@intel.com>
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
next reply other threads:[~2019-04-17 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 13:19 xuyanjie [this message]
2019-04-17 18:58 ` Rami Rosen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1555507177-171382-1-git-send-email-yanjie.xu@intel.com \
--to=yanjie.xu@intel.com \
--cc=dts@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).