summaryrefslogtreecommitdiff
path: root/drivers/net/ethernet/ni
diff options
context:
space:
mode:
authorWojciech Drewek <wojciech.drewek@intel.com>2021-08-20 03:08:49 +0300
committerTony Nguyen <anthony.l.nguyen@intel.com>2021-10-07 20:41:41 +0300
commit2ae0aa4758b0f4a247d45cb3bf01548a7f396751 (patch)
tree1239a01c593922709ab716e09b1c3589fad04ec2 /drivers/net/ethernet/ni
parent3ea9bd5d023177d6a792623509a55590b19ecbe7 (diff)
downloadlinux-2ae0aa4758b0f4a247d45cb3bf01548a7f396751.tar.xz
ice: Move devlink port to PF/VF struct
Keeping devlink port inside VSI data structure causes some issues. Since VF VSI is released during reset that means that we have to unregister devlink port and register it again every time reset is triggered. With the new changes in devlink API it might cause deadlock issues. After calling devlink_port_register/devlink_port_unregister devlink API is going to lock rtnl_mutex. It's an issue when VF reset is triggered in netlink operation context (like setting VF MAC address or VLAN), because rtnl_lock is already taken by netlink. Another call of rtnl_lock from devlink API results in dead-lock. By moving devlink port to PF/VF we avoid creating/destroying it during reset. Since this patch, devlink ports are created during ice_probe, destroyed during ice_remove for PF and created during ice_repr_add, destroyed during ice_repr_rem for VF. Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com> Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Diffstat (limited to 'drivers/net/ethernet/ni')
0 files changed, 0 insertions, 0 deletions