| commit | a38488f54004330071f4ec90c3cf52dc7646468e | |
| author | Jacob Keller <jacob.e.keller@intel.com> | |
| Wed, 3 Jun 2015 23:31:07 +0000 (3 16:31 -0700) | ||
| committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | |
| Wed, 17 Jun 2015 21:21:15 +0000 (17 14:21 -0700) | ||
| tree | a8100050b82b616c6495eb8eb45d99244630cbd2 | treesnapshot (tar.gz zip) |
| parent | c04ae58e2b6d836325914e7b4aa25f43da1be3df | commitdiff |
fm10k: force LPORT delete when updating VLAN or MAC address
Currently, we don't notify the switch at all when the PF
administratively sets a new VLAN or MAC address. This causes the old
addresses to remain valid on the switch table. Since the PF is
overriding any configuration done directly by the VF, we choose to
simply re-create the LPORT for the VF. This does mean that all rules for
the VF will be dropped when we set something directly via the PF, but it
prevents some weird issues where the MAC/VLAN table retains some stale
configuration.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Tested-by: Krishneil Singh <Krishneil.k.singh@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Currently, we don't notify the switch at all when the PF
administratively sets a new VLAN or MAC address. This causes the old
addresses to remain valid on the switch table. Since the PF is
overriding any configuration done directly by the VF, we choose to
simply re-create the LPORT for the VF. This does mean that all rules for
the VF will be dropped when we set something directly via the PF, but it
prevents some weird issues where the MAC/VLAN table retains some stale
configuration.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Tested-by: Krishneil Singh <Krishneil.k.singh@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
| drivers/net/ethernet/intel/fm10k/fm10k_iov.c | diffblobblamehistory |