From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 17603A05D3 for ; Mon, 25 Mar 2019 08:23:55 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CEBED3256; Mon, 25 Mar 2019 08:23:54 +0100 (CET) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 5D7292C19 for ; Mon, 25 Mar 2019 08:23:53 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Mar 2019 00:23:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,256,1549958400"; d="scan'208";a="217275638" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga001.jf.intel.com with ESMTP; 25 Mar 2019 00:23:51 -0700 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 25 Mar 2019 00:23:51 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 25 Mar 2019 00:23:51 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.134]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.26]) with mapi id 14.03.0415.000; Mon, 25 Mar 2019 15:23:48 +0800 From: "Mei, JianweiX" To: "Tu, Lijuan" , "dts@dpdk.org" Thread-Topic: [dts] [PATCH V2] test_plans/etag: add hardware informations Thread-Index: AQHU4hTZwVpul9Y/3UyddSes5hUiPKYb8iaA Date: Mon, 25 Mar 2019 07:23:48 +0000 Message-ID: <8492B1A1F60DBB41A65FD160BBB3DA8BF7D44E@SHSMSX103.ccr.corp.intel.com> References: <1553236276-75799-1-git-send-email-jianweix.mei@intel.com> <8CE3E05A3F976642AAB0F4675D0AD20E0BA4588A@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BA4588A@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V2] test_plans/etag: add hardware informations X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" Hi Lijuan, You are right, the NIC X550 support E-tag too, I'll update the test plan, t= hanks for checking this. -----Original Message----- From: Tu, Lijuan=20 Sent: Sunday, March 24, 2019 3:40 PM To: Mei, JianweiX ; dts@dpdk.org Cc: Mei, JianweiX 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 > Subject: [dts] [PATCH V2] test_plans/etag: add hardware informations >=20 >=20 > modify x550 to X552/X557 and add hardware infos >=20 > Signed-off-by: Jianwei Mei > --- > test_plans/etag_test_plan.rst | 29 ++++++++++++++++++++++++----- > 1 file changed, 24 insertions(+), 5 deletions(-) >=20 > diff --git a/test_plans/etag_test_plan.rst=20 > 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=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D >=20 > In some systems an additional external tag (E-tag) can be present=20 > 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=20 > identify a subsystem (usually a VM) and the near end switch adds a tag=20 > indicating the destination subsystem. >=20 > -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 @@=20 > -49,19 +49,38 @@ The support of E-tag features by X550 consists in: > Prerequisites > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > +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=20 > +the > product name. > + > +2. Bios: > + > +- Enable etag items in BIOS > + > +3. Software: > + > +- DPDK: http://dpdk.org/git/dpdk > + > +Set up scenario > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > 1. Create 2VF devices from PF device:: >=20 > ./dpdk_nic_bind.py --st > 0000:84:00.0 'Device 1563' drv=3Digb_uio unused=3D > echo 2 > /sys/bus/pci/devices/0000\:84\:00.0/max_vfs >=20 > -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:: >=20 > /sbin/modprobe pci-stub >=20 > - using `lspci -nn|grep -i ethernet` got VF device id, for example "80= 86 1565":: > + using `lspci -nn|grep -i ethernet` got VF device id, for example "80= 86:15ad":: >=20 > - 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/unbi= nd > echo 0000:84:10.0 > /sys/bus/pci/drivers/pci-stub/bind > echo 0000:84:10.2 >=20 > /sys/bus/pci/devices/0000:84:10.2/driver/unbind > -- > 2.17.2