[dts] [PATCH V2] test_plans/etag: add hardware informations

[Zhu, ShuaiX]

Tested-by: Zhu, ShuaiX <shuaix.zhu at intel.com>

> -----Original Message-----
> From: dts [mailto:dts-bounces at dpdk.org] On Behalf Of Jianwei Mei
> Sent: Friday, March 22, 2019 2:31 PM
> To: dts at dpdk.org
> Cc: Mei, JianweiX <jianweix.mei at intel.com>
> Subject: [dts] [PATCH V2] test_plans/etag: add hardware informations
> 
> 
> modify x550 to X552/X557 and add hardware infos
> 
> Signed-off-by: Jianwei Mei <jianweix.mei at 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