bnxt_en: Don't use rtnl lock to protect link change logic in workqueue.

Browse source

As a further improvement to the PF/VF link change logic, use a private
mutex instead of the rtnl lock to protect link change logic.  With the
new mutex, we don't have to take the rtnl lock in the workqueue when
we have to handle link related functions.  If the VF and PF drivers
are running on the same host and both take the rtnl lock and one is
waiting for the other, it will cause timeout.  This patch fixes these
timeouts.

Fixes: 90c694bb71 ("bnxt_en: Fix RTNL lock usage on bnxt_update_link().")
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

...

This commit is contained in:

Michael Chan 2017-10-13 21:09:30 -04:00 • committed by David S. Miller

parent c213eae8d3

commit e2dc9b6e38

3 changed files with 21 additions and 12 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

25

drivers/net/ethernet/broadcom/bnxt/bnxt.c

View file

4

drivers/net/ethernet/broadcom/bnxt/bnxt.h

View file

4

drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c

View file