From: Jianwei Mei <jianweix.mei@intel.com>
To: dts@dpdk.org
Cc: Jianwei Mei <jianweix.mei@intel.com>
Subject: [dts] [PATCH V2] test_plans/etag: add hardware informations
Date: Fri, 22 Mar 2019 14:31:16 +0800 [thread overview]
Message-ID: <1553236276-75799-1-git-send-email-jianweix.mei@intel.com> (raw)
modify x550 to X552/X557 and add hardware infos
Signed-off-by: Jianwei Mei <jianweix.mei@intel.com>
---
test_plans/etag_test_plan.rst | 29 ++++++++++++++++++++++++-----
1 file changed, 24 insertions(+), 5 deletions(-)
diff --git a/test_plans/etag_test_plan.rst b/test_plans/etag_test_plan.rst
index 6350d64..f643a12 100644
--- a/test_plans/etag_test_plan.rst
+++ b/test_plans/etag_test_plan.rst
@@ -35,12 +35,12 @@ External Tag (E-tag) Tests
==========================
In some systems an additional external tag (E-tag) can be present before the
-VLAN. NIC X550 support VLANs in presence of external tags.
+VLAN. NIC X552/X557 support VLANs in presence of external tags.
E-tag mode is used for systems where the device adds a tag to identify a
subsystem (usually a VM) and the near end switch adds a tag indicating the
destination subsystem.
-The support of E-tag features by X550 consists in:
+The support of E-tag features by X552/X557 consists in:
- The filtering of received E-tag packets
- E-tag header stripping by VF device in received packets
- E-tag header insertion by VF device in transmitted packets
@@ -49,19 +49,38 @@ The support of E-tag features by X550 consists in:
Prerequisites
=============
+1. Hardware:
+
+- Machine type: SuperMicro 1U Xeon D Broadwell SoC uServer
+- Product Name: SYS-5018D-FN4T
+- Nic: Sagepond(X552/X557-AT)
+
+Note: you can use "dmidecode | grep 'Product Name'" command to get the product name.
+
+2. Bios:
+
+- Enable etag items in BIOS
+
+3. Software:
+
+- DPDK: http://dpdk.org/git/dpdk
+
+Set up scenario
+===============
+
1. Create 2VF devices from PF device::
./dpdk_nic_bind.py --st
0000:84:00.0 'Device 1563' drv=igb_uio unused=
echo 2 > /sys/bus/pci/devices/0000\:84\:00.0/max_vfs
-2. Detach VFs from the host, bind them to pci-stub driver::
+2. Detach VFs from the host, bind them to pci-stub or vfio-pci driver::
/sbin/modprobe pci-stub
- using `lspci -nn|grep -i ethernet` got VF device id, for example "8086 1565"::
+ using `lspci -nn|grep -i ethernet` got VF device id, for example "8086:15ad"::
- echo "8086 1565" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo "8086:15ad" > /sys/bus/pci/drivers/pci-stub/new_id
echo 0000:84:10.0 > /sys/bus/pci/devices/0000:84:10.0/driver/unbind
echo 0000:84:10.0 > /sys/bus/pci/drivers/pci-stub/bind
echo 0000:84:10.2 > /sys/bus/pci/devices/0000:84:10.2/driver/unbind
--
2.17.2
next reply other threads:[~2019-03-22 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 6:31 Jianwei Mei [this message]
2019-03-22 6:30 ` Zhu, ShuaiX
2019-03-24 7:40 ` Tu, Lijuan
2019-03-25 7:23 ` Mei, JianweiX
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=1553236276-75799-1-git-send-email-jianweix.mei@intel.com \
--to=jianweix.mei@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).