From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <qian.q.xu@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id A0BAF8D99
 for <dev@dpdk.org>; Mon, 25 Jan 2016 07:22:58 +0100 (CET)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
 by orsmga102.jf.intel.com with ESMTP; 24 Jan 2016 22:22:57 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,343,1449561600"; d="scan'208";a="900430474"
Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204])
 by fmsmga002.fm.intel.com with ESMTP; 24 Jan 2016 22:22:57 -0800
Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by
 FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Sun, 24 Jan 2016 22:22:56 -0800
Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by
 FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Sun, 24 Jan 2016 22:22:56 -0800
Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.172]) by
 SHSMSX101.ccr.corp.intel.com ([169.254.1.215]) with mapi id 14.03.0248.002;
 Mon, 25 Jan 2016 14:22:54 +0800
From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, "Tao, Zhe"
 <zhe.tao@intel.com>, "Mcnamara, John" <john.mcnamara@intel.com>
Thread-Topic: [dpdk-dev] [PATCH] i40e: add VEB switching support for i40e
Thread-Index: AQHRVBgOXGQ4YzG4e0SePar7XGHvrp8GzYwAgAT3dkA=
Date: Mon, 25 Jan 2016 06:22:53 +0000
Message-ID: <82F45D86ADE5454A95A89742C8D1410E031BD396@shsmsx102.ccr.corp.intel.com>
References: <1453358984-20550-1-git-send-email-zhe.tao@intel.com>
 <1954959.nPV1f2ZDDs@xps13>
In-Reply-To: <1954959.nPV1f2ZDDs@xps13>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNDQyODU3ZGEtOGJlOC00MTM0LTg2N2YtMjQ1ODBjMzY3OTI3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVzkxMVwvRHpjaWZBRnVzOEpDakdDWmxMZlY0c3FKVktsMVwvK2NnN2FtZ0drPSJ9
x-ctpclassification: CTP_IC
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] i40e: add VEB switching support for i40e
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2016 06:22:59 -0000

I have a quick check, VEB/VEPA/VSI is not i40e's specific, they are IEEE EV=
B terms. See below.=20

IEEE EVB tutorial: http://www.ieee802.org/802_tutorials/2009-11/evb-tutoria=
l-draft-20091116_v09.pdf

Virtual Ethernet Bridge (VEB) - This is an IEEE EVB term. A VEB is a VLAN B=
ridge internal to Fortville that bridges the traffic of multiple VSIs over =
an internal virtual network.=20
Virtual Ethernet Port Aggregator (VEPA) - This is an IEEE EVB term. A VEPA =
multiplexes the traffic of one or more VSIs onto a single Fortville Etherne=
t port. The biggest difference between a VEB and a VEPA is that a VEB can s=
witch packets internally between VSIs, whereas a VEPA cannot.=20
Virtual Station Interface (VSI) - This is an IEEE EVB term that defines the=
 properties of a virtual machine's (or a physical machine's) connection to =
the network. Each downstream v-port on a Fortville VEB or VEPA defines a VS=
I. A standards-based definition of VSI properties enables network managemen=
t tools to perform virtual machine migration and associated network re-conf=
iguration in a vendor-neutral manner.



Thanks
Qian

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Friday, January 22, 2016 6:16 PM
To: Tao, Zhe; Mcnamara, John
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] i40e: add VEB switching support for i40e

2016-01-21 14:49, Zhe Tao:
> VEB switching feature for i40e is used to enable the switching between=20
> the  VSIs connect to the virtual bridge. The old implementation is=20
> setting the  virtual bridge mode as VEPA which is port aggregation.=20
> Enable the switching  ability by setting the loop back mode for the=20
> specific VSIs which connect to PF  or VFs.
>=20
> Signed-off-by: Zhe Tao <zhe.tao@intel.com>

Is VEB something specific to i40e?
Please explain the acronyms VEB, VSI and VEPA in the commit log or in a doc=
 dedicated to i40e. Having some design explanations in a doc would help to =
understand the changes and to contribute.
Thanks