Go to file

Jan Gutter f4329ffe18 Improve OVS Representor VF Lookup

This patch set addresses some of the concerns outlined in:
https://bugs.launchpad.net/os-vif/+bug/1704485

* Determining the VF number from the netdev's phys_port_name:
  phys_port_name is read and then cast to an int.

  Currently there is no standard method to associate a representor with
  the VF number.
  phys_port_name has emerged as the "default" choice, but merely casting
  it as a single number has shortcomings:

  * A switchdev can potentially have VFs, PFs and physical ports as
    representors.
  * A switchdev can have multiple PFs.

  In this case, the recommendation is to use a parse tree that accepts
  naming conventions like:

  * 42
  * vf42
  * PF1VF42
  * vf42@PF1

* Test cases have been added for the above scenarios.

* An internal function for PF matching has been added for future use.
  This is important when PF representors are eventually exposed.

Change-Id: I051fcc6fd136b389a6200076bd6fc3b73b626d5e
Closes-Bug: #1704485
Signed-off-by: Jan Gutter <jan.gutter@netronome.com>

2017-07-19 14:40:59 -04:00

doc/source

Add support for VIFPortProfileOVSRepresentor

2017-07-18 20:56:55 +00:00

os_vif

Add support for VIFPortProfileOVSRepresentor

2017-07-18 20:56:55 +00:00

releasenotes

Add support for VIFPortProfileOVSRepresentor

2017-07-18 20:56:55 +00:00

vif_plug_linux_bridge

set mtu on all code paths