diff options
| author | Jacob Keller <[email protected]> | 2018-01-24 14:20:29 -0800 |
|---|---|---|
| committer | Jeff Kirsher <[email protected]> | 2018-01-24 14:20:29 -0800 |
| commit | 74d2950c8055a631e196349dd1345ff6deb11c73 (patch) | |
| tree | dc7f42fef6717df371dc023655d41b8c85f5937c /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 8c2c5039073849d5b6f9cedaea604ebab1a50dc8 (diff) | |
fm10k: don't assume VLAN 1 is enabled
Since commit 856dfd69e84f ("fm10k: Fix multicast mode synch issues",
2016-03-03) we've incorrectly assumed that VLAN 1 is enabled when the
default VID is not set.
This occurs because we check the default_vid and if it's zero, start
several loops over the active_vlans bitmask at 1, instead of checking to
ensure that that bit is active.
This happened because of commit d9ff3ee8efe9 ("fm10k: Add support for
VLAN 0 w/o default VLAN", 2014-08-07) which mistakenly assumed that we
should send requests for MAC and VLAN filters with VLAN 0 when the
default_vid isn't set.
However, the switch generally considers this an invalid configuration,
so the only time we'd have a default_vid of 0 is when the switch is
down.
Instead, lets just not request any filters for the default_vid if it's
not yet been assigned.
Signed-off-by: Jacob Keller <[email protected]>
Tested-by: Krishneil Singh <[email protected]>
Signed-off-by: Jeff Kirsher <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions