kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1540435

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1540435

Title:
  Introducing ConnectX-4 Ethernet SRIOV

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This patchset introduces the support of Ethernet SRIOV in ConnectX-4 
  family of 100G Ethernet NICs.

  Basic Introduction:
  ConnectX-4 HW architecture provides two kinds of underlying HW switches.

  MPFS (Multi Physical Function Switch) or L2 Table in Software terms:

  The HCA has one MPFS switch per physical port, this switch is responsible
  of forwarding Unicast traffic to the various overlying Physical Functions (PFs). 
  Multicast traffic is flooded amongst all the PFs, Each PF can request to
  forward a unicast MAC to its E-Switch Uplink vport (which we will cover later) 
  through SET_L2_TABLE_ENTRY HW command.

  MPFS has five ports, four are connected to PFs (one for each) and one is connected 
  directly to the Physical Port (Physical Link).

  E-Switch (Ethernet Switch):

  The HCA has one per physical function. The main responsibility of this component is 
  to forward Unicast/Multicast and vlan tagged/untagged traffic to the various 
  Virtual Functions (VFs) allocated by the PF. Unlike MPFS, the PF needs to explicitly 
  create the E-Switch FDB table, Which is a HW flow table managed by the PF driver 
  whenever vport_group_manager capability bit is set for this PF.

  E-Switch has Virtual Ports (vports) entities as its ports, vport0 and uplink vport
  are special kind of vports that represents PF vport (vport0) and uplink vport which
  is connected to the MPFS switch (if exists) as the PF external link.
  vport1..vportN represent VF0..VF(N-1) egress/ingress ports.

  E-Switch FDB contains forwarding rules such as:
          UC MAC0 -> vport0(PF).
          UC MAC1 -> vport1.
          UC MAC2 -> vport2.
          MC MACX -> vport0, vport2, Uplink.
          MC MACY -> vport1, Uplink.
      
      For unmatched traffic FDB has the following default rules:
          Unmatched Traffic (src vport != Uplink) -> Uplink.
          Unmatched Traffic (src vport == Uplink) -> vport0(PF).

  NIC VPort context: 
  Each NIC (VF/PF) has its own vport context which will be used to store the current
  NIC vport context (UC/MC and vlan lists) and other NIC properties such as MTU, promisc 
  mode, etc.. NIC (VF/PF) driver is responsible of constantly updating this context.

  FDB rules population:
  Each NIC vport (VF/PF) will notify E-Switch manager of its UC/MC vport
  context changes via modify vport context command, which will be
  translated to an event that will be handled by E-Switch manager (PF)
  which will update FDB table accordingly.

  Both PF and VF use the same driver and submit commands directly to the firmware.
  The PF sees the vport_group_manager capability bit and as such runs the code
  to populate the embedded switches as explained above.

  The patch goes as follows:

  Patches 1-2 introduces the basic PCI SRIOV functionalities and the support of
  Connectx4 to enable specific VFs via enable/disable HCA commands. These two
  patches will be also in use later for the IB SRIOV flow.

  Patches 3-8 Introduces the basic E-Switch capabilities and commands to be used later by
  VF to modify and update its NIC vport context, and by PF (E-Switch Manager) driver to
  Query the VF NIC context and acts accordingly.

  Patches 9-10 Provide the needed functionality of a NIC driver VF/PF to support SRIOV,
  mainly vport context update support.

  Patch 11 ("net/mlx5: Introducing E-Switch and l2 table"), Introduces the basic
  E-Switch support and infrastructure to read vport context events and to update
  MPFS L2 Table of the UC mac addresses request by the PF.

  Patches 12-18 Introduces SRIOV enablemenet and E-Switch FDB table management
  It adds the Basic E-Swtich public API to set and get sriov properties to be used
  in PF netdev sriov ndos.

  Patchset was applied ontop of commit 3f8c0f7 "gianfar: use
  of_property_read_bool()"

  Saeed, Eli and Or.

  Eli Cohen (2):
    net/mlx5_core: Modify enable/disable hca functions
    net/mlx5_core: Add base sriov support

  Saeed Mahameed (18):
    net/mlx5: Add HW capabilities and structs for SR-IOV E-Switch.
    net/mlx5: Update access functions to Query/Modify vport MAC address
    net/mlx5: Introduce access functions to modify/query vport mac lists
    net/mlx5: Introduce access functions to modify/query vport state
    net/mlx5: Introduce access functions to modify/query vport promisc mode
    net/mlx5: Introduce access functions to modify/query vport vlans
    net/mlx5e: Write UC/MC list and promisc mode into vport context
    net/mlx5e: Write vlan list into vport context
    net/mlx5: Introducing E-Switch and l2 table
    net/mlx5: E-Switch, Introduce FDB hardware capabilities
    net/mlx5: E-Switch, Add SR-IOV (FDB) support
    net/mlx5: E-Switch, Introduce Vport administration functions
    net/mlx5: E-Switch, Introduce HCA cap and E-Switch vport context
    net/mlx5: E-Switch, Introduce set vport vlan (VST mode)
    net/mlx5: E-Switch, Introduce get vf statistics
    net/mlx5e: Add support for SR-IOV ndos
   net/mlx5e: Assign random MAC address if needed
   net/mlx5: Fix query E-Switch capabilities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540435/+subscriptions