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>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] i40e: add VEB switching support for i40e
Date: Mon, 25 Jan 2016 06:22:53 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E031BD396@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1954959.nPV1f2ZDDs@xps13>
I have a quick check, VEB/VEPA/VSI is not i40e's specific, they are IEEE EVB terms. See below.
IEEE EVB tutorial: http://www.ieee802.org/802_tutorials/2009-11/evb-tutorial-draft-20091116_v09.pdf
Virtual Ethernet Bridge (VEB) - This is an IEEE EVB term. A VEB is a VLAN Bridge internal to Fortville that bridges the traffic of multiple VSIs over an internal virtual network.
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 Ethernet port. The biggest difference between a VEB and a VEPA is that a VEB can switch packets internally between VSIs, whereas a VEPA cannot.
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 VSI. A standards-based definition of VSI properties enables network management tools to perform virtual machine migration and associated network re-configuration 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
> the VSIs connect to the virtual bridge. The old implementation is
> setting the virtual bridge mode as VEPA which is port aggregation.
> Enable the switching ability by setting the loop back mode for the
> specific VSIs which connect to PF or VFs.
>
> 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
next prev parent reply other threads:[~2016-01-25 6:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 6:49 Zhe Tao
2016-01-22 10:16 ` Thomas Monjalon
2016-01-25 6:22 ` Xu, Qian Q [this message]
2016-02-19 5:17 ` Wu, Jingjing
2016-02-23 3:48 ` Zhe Tao
2016-02-23 8:10 ` [dpdk-dev] [PATCH v2] " Zhe Tao
2016-02-25 0:42 ` Wu, Jingjing
2016-03-09 5:38 ` [dpdk-dev] [PATCH v3] " Zhe Tao
2016-03-09 6:02 ` Wu, Jingjing
2016-03-11 21:50 ` Bruce Richardson
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=82F45D86ADE5454A95A89742C8D1410E031BD396@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=zhe.tao@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).