[dpdk-dev,v3] i40e: add VEB switching support for i40e
Commit Message
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.
VEB/VSI/VEPA are concepts not specific to the i40e HW, the concepts are from
802.1qbg spec
IEEE EVB tutorial:
http://www.ieee802.org/802_tutorials/2009-11/evb-tutorial-draft-20091116_v09.pdf
VEB: a virtual switch can forward the packet based on the specific match field.
VSI: a virtual interface connect between the VEB/VEPA and virtual machine.
VEPA: a virtual Ethernet port aggregator will upstream the packets from VSI to
the LAN port.
Signed-off-by: Zhe Tao <zhe.tao@intel.com>
---
v1: Add the VEB switching support.
v2: Add the check for the FW version, which should larger than 5.0.
Add release note.
v3: Add the VEB concepts description in the commit log.
doc/guides/rel_notes/release_16_04.rst | 1 +
drivers/net/i40e/i40e_ethdev.c | 57 +++++++++++++++++++++++++++++-----
2 files changed, 50 insertions(+), 8 deletions(-)
Comments
> -----Original Message-----
> From: Tao, Zhe
> Sent: Wednesday, March 09, 2016 1:39 PM
> To: dev@dpdk.org
> Cc: Tao, Zhe; Wu, Jingjing
> Subject: [dpdk-dev][PATCH v3] i40e: add VEB switching support for i40e
>
> 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.
>
> VEB/VSI/VEPA are concepts not specific to the i40e HW, the concepts are
> from 802.1qbg spec IEEE EVB tutorial:
> http://www.ieee802.org/802_tutorials/2009-11/evb-tutorial-draft-
> 20091116_v09.pdf
>
> VEB: a virtual switch can forward the packet based on the specific match field.
> VSI: a virtual interface connect between the VEB/VEPA and virtual machine.
> VEPA: a virtual Ethernet port aggregator will upstream the packets from VSI
> to the LAN port.
>
> Signed-off-by: Zhe Tao <zhe.tao@intel.com>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
On Wed, Mar 09, 2016 at 06:02:38AM +0000, Wu, Jingjing wrote:
>
>
> > -----Original Message-----
> > From: Tao, Zhe
> > Sent: Wednesday, March 09, 2016 1:39 PM
> > To: dev@dpdk.org
> > Cc: Tao, Zhe; Wu, Jingjing
> > Subject: [dpdk-dev][PATCH v3] i40e: add VEB switching support for i40e
> >
> > 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.
> >
> > VEB/VSI/VEPA are concepts not specific to the i40e HW, the concepts are
> > from 802.1qbg spec IEEE EVB tutorial:
> > http://www.ieee802.org/802_tutorials/2009-11/evb-tutorial-draft-
> > 20091116_v09.pdf
> >
> > VEB: a virtual switch can forward the packet based on the specific match field.
> > VSI: a virtual interface connect between the VEB/VEPA and virtual machine.
> > VEPA: a virtual Ethernet port aggregator will upstream the packets from VSI
> > to the LAN port.
> >
> > Signed-off-by: Zhe Tao <zhe.tao@intel.com>
> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
>
Applied to dpdk-next-net/rel_16_04
/Bruce
@@ -46,6 +46,7 @@ This section should contain new features added in this release. Sample format:
* **Added vhost-user live migration support.**
+* **Added VEB switching support for FVL.**
Resolved Issues
---------------
@@ -3822,6 +3822,45 @@ i40e_vsi_get_bw_config(struct i40e_vsi *vsi)
return I40E_SUCCESS;
}
+/* i40e_enable_pf_lb
+ * @pf: pointer to the pf structure
+ *
+ * allow loopback on pf
+ */
+static inline void
+i40e_enable_pf_lb(struct i40e_pf *pf)
+{
+ struct i40e_hw *hw = I40E_PF_TO_HW(pf);
+ struct i40e_vsi_context ctxt;
+ int ret;
+
+ /* Use the FW API if FW >= v5.0 */
+ if (hw->aq.fw_maj_ver < 5) {
+ PMD_INIT_LOG(ERR, "FW < v5.0, cannot enable loopback");
+ return;
+ }
+
+ memset(&ctxt, 0, sizeof(ctxt));
+ ctxt.seid = pf->main_vsi_seid;
+ ctxt.pf_num = hw->pf_id;
+ ret = i40e_aq_get_vsi_params(hw, &ctxt, NULL);
+ if (ret) {
+ PMD_DRV_LOG(ERR, "cannot get pf vsi config, err %d, aq_err %d",
+ ret, hw->aq.asq_last_status);
+ return;
+ }
+ ctxt.flags = I40E_AQ_VSI_TYPE_PF;
+ ctxt.info.valid_sections =
+ rte_cpu_to_le_16(I40E_AQ_VSI_PROP_SWITCH_VALID);
+ ctxt.info.switch_id |=
+ rte_cpu_to_le_16(I40E_AQ_VSI_SW_ID_FLAG_ALLOW_LB);
+
+ ret = i40e_aq_update_vsi_params(hw, &ctxt, NULL);
+ if (ret)
+ PMD_DRV_LOG(ERR, "update vsi switch failed, aq_err=%d\n",
+ hw->aq.asq_last_status);
+}
+
/* Setup a VSI */
struct i40e_vsi *
i40e_vsi_setup(struct i40e_pf *pf,
@@ -3857,6 +3896,8 @@ i40e_vsi_setup(struct i40e_pf *pf,
PMD_DRV_LOG(ERR, "VEB setup failed");
return NULL;
}
+ /* set ALLOWLOOPBACk on pf, when veb is created */
+ i40e_enable_pf_lb(pf);
}
vsi = rte_zmalloc("i40e_vsi", sizeof(struct i40e_vsi), 0);
@@ -4029,14 +4070,14 @@ i40e_vsi_setup(struct i40e_pf *pf,
ctxt.connection_type = 0x1;
ctxt.flags = I40E_AQ_VSI_TYPE_VF;
- /**
- * Do not configure switch ID to enable VEB switch by
- * I40E_AQ_VSI_SW_ID_FLAG_ALLOW_LB. Because in Fortville,
- * if the source mac address of packet sent from VF is not
- * listed in the VEB's mac table, the VEB will switch the
- * packet back to the VF. Need to enable it when HW issue
- * is fixed.
- */
+ /* Use the VEB configuration if FW >= v5.0 */
+ if (hw->aq.fw_maj_ver >= 5) {
+ /* Configure switch ID */
+ ctxt.info.valid_sections |=
+ rte_cpu_to_le_16(I40E_AQ_VSI_PROP_SWITCH_VALID);
+ ctxt.info.switch_id =
+ rte_cpu_to_le_16(I40E_AQ_VSI_SW_ID_FLAG_ALLOW_LB);
+ }
/* Configure port/vlan */
ctxt.info.valid_sections |=