diff options
author | 2014-02-05 15:13:02 +0200 | |
---|---|---|
committer | 2014-02-13 14:31:09 -0800 | |
commit | ad4885d279b63c65347220236d07669a2f59634b (patch) | |
tree | 1d540ca627bc2b997320384dda5bd9d7907f40e9 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | IB/mlx4: Do IBoE GID table resets per-port (diff) | |
download | linux-dev-ad4885d279b63c65347220236d07669a2f59634b.tar.xz linux-dev-ad4885d279b63c65347220236d07669a2f59634b.zip |
IB/mlx4: Build the port IBoE GID table properly under bonding
When scanning netdevices we need to check a few more conditions and
cases to build the IBoE GID table properly. For example, under
bonding we must make sure that when a port is down, the bond IP
address isn't programmed as a GID, since doing so will cause failure
with IB core flows that selects ports by GID.
Signed-off-by: Moni Shoua <monis@mellanox.co.il>
Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
Signed-off-by: Roland Dreier <roland@purestorage.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions