From: "Mei, JianweiX" <jianweix.mei@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V2] test_plans/etag: add hardware informations
Date: Mon, 25 Mar 2019 07:23:48 +0000 [thread overview]
Message-ID: <8492B1A1F60DBB41A65FD160BBB3DA8BF7D44E@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BA4588A@SHSMSX101.ccr.corp.intel.com>
Hi Lijuan,
You are right, the NIC X550 support E-tag too, I'll update the test plan, thanks for checking this.
-----Original Message-----
From: Tu, Lijuan
Sent: Sunday, March 24, 2019 3:40 PM
To: Mei, JianweiX <jianweix.mei@intel.com>; dts@dpdk.org
Cc: Mei, JianweiX <jianweix.mei@intel.com>
Subject: RE: [dts] [PATCH V2] test_plans/etag: add hardware informations
Hi Jianwei,
Change X550 to X552/x557 will confuse user that X550 not support E-tag, but actually it supports.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Jianwei Mei
> Sent: Thursday, March 21, 2019 11:31 PM
> To: dts@dpdk.org
> Cc: Mei, JianweiX <jianweix.mei@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@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
prev parent reply other threads:[~2019-03-25 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 6:31 Jianwei Mei
2019-03-22 6:30 ` Zhu, ShuaiX
2019-03-24 7:40 ` Tu, Lijuan
2019-03-25 7:23 ` Mei, JianweiX [this message]
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=8492B1A1F60DBB41A65FD160BBB3DA8BF7D44E@SHSMSX103.ccr.corp.intel.com \
--to=jianweix.mei@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
/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).