From: "Mei, JianweiX" <jianweix.mei@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V3] test_plans/etag:add hardware informations
Date: Mon, 8 Apr 2019 02:21:48 +0000 [thread overview]
Message-ID: <8492B1A1F60DBB41A65FD160BBB3DA8BF853BD@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BA5B474@SHSMSX101.ccr.corp.intel.com>
Ok, thanks for your review.
-----Original Message-----
From: Tu, Lijuan
Sent: Thursday, April 4, 2019 12:05 AM
To: Mei, JianweiX <jianweix.mei@intel.com>; dts@dpdk.org
Cc: Mei, JianweiX <jianweix.mei@intel.com>
Subject: RE: [dts] [PATCH V3] test_plans/etag:add hardware informations
Sagepond(X552/X557-AT) is a build-in NIC in SuperMicro 1U Xeon D Broadwell SoC uServer, but Sageville(X550) is a separated NIC that we can install it in any machines, so it doesn't make sense to add your machine type in prerequisites, because it's not a MUST option, but a COULD option. I prefer to remove 'Machine type' and 'Product Name'
> +- Machine type: SuperMicro 1U Xeon D Broadwell SoC uServer
> +- Product Name: SYS-5018D-FN4T
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Jianwei Mei
> Sent: Monday, March 25, 2019 1:37 AM
> To: dts@dpdk.org
> Cc: Mei, JianweiX <jianweix.mei@intel.com>
> Subject: [dts] [PATCH V3] test_plans/etag:add hardware informations
[Lijuan] typo, informations -> information
>
> add hardware informations
>
> Signed-off-by: Jianwei Mei <jianweix.mei@intel.com>
> ---
> test_plans/etag_test_plan.rst | 25 ++++++++++++++++++++++---
> 1 file changed, 22 insertions(+), 3 deletions(-)
>
> diff --git a/test_plans/etag_test_plan.rst
> b/test_plans/etag_test_plan.rst index 6350d64..43d7121 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 X550 and 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 X550 and 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 @@ -48,6
> +48,25 @@ 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: Sageville(X550) and 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
[Lijuan] it's better to tell where can found the etag items, such as AA->BB->CC->DD
> +
> +3. Software:
> +
> +- DPDK: http://dpdk.org/git/dpdk
> +
> +
> +Set up scenario
> +===============
>
> 1. Create 2VF devices from PF device::
>
> @@ -55,7 +74,7 @@ Prerequisites
> 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
>
> --
> 2.17.2
prev parent reply other threads:[~2019-04-08 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 8:36 Jianwei Mei
2019-03-25 8:52 ` Zhu, ShuaiX
2019-04-03 16:05 ` Tu, Lijuan
2019-04-08 2:21 ` 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=8492B1A1F60DBB41A65FD160BBB3DA8BF853BD@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).