linux

iv/linux

History

Ngai-Mint Kwan 7d4fe0d123 fm10k: do not enqueue mailbox when host not ready

Interfaces will reset whenever the TX mailbox FIFO has become full. This
occurs more frequently whenever the IES API application is not running
to process and clear the messages in the FIFO. Thus, this could lead to
situations where the interface would enter an infinite reset loop. That
is: if the interface is trying to synchronize a huge number of unicast
and multicast entries with the IES API application, the TX mailbox FIFO
will become full and the interface resets. Once the interface exits
reset, it'll try to synchronize the unicast and multicast entries again.
Ergo, this creates an infinite loop. Other actions such as multiple
mulitcast mode or up/down transitions will fill the TX mailbox FIFO and
induce the interface to reset. To correct these situations, check if the
interface's "host_ready" flag is enabled before enqueuing any messages
to the TX mailbox FIFO. This check will be conducted by a function call.
Lastly, this issue mainly affects the PF and, thus, the VF is exempt.

Signed-off-by: Ngai-Mint Kwan <ngai-mint.kwan@intel.com>
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>

2017-04-05 22:47:31 -07:00

fm10k_common.c

fm10k-shared: use mac-> instead of hw->mac.

2017-01-08 01:22:57 -08:00

fm10k_common.h

fm10k: prefer READ_ONCE instead of ACCESS_ONCE

2016-08-29 01:31:03 -07:00

fm10k_dcbnl.c

fm10k: consistently use Intel(R) for driver names

2016-04-20 23:07:34 -07:00

fm10k_debugfs.c

fm10k: consistently use Intel(R) for driver names