Searched hist:"9 ce0e8d72678b5b60c99ce4c7af15ec127c761cb" (Results 1 – 2 of 2) sorted by relevance
/linux/drivers/net/ethernet/intel/igbvf/ |
H A D | mbx.c | diff 9ce0e8d72678b5b60c99ce4c7af15ec127c761cb Sat Dec 12 01:45:38 CET 2015 Mitch Williams <mitch.a.williams@intel.com> igb/igbvf: don't give up
The driver shouldn't just give up if it fails to get the hardware mailbox lock. This can happen in a situation where the PF-VF communication channel is heavily loaded and causes complete communications failure between the PF and VF drivers.
Add a counter and a delay. The driver will now retry ten times, waiting one millisecond between retries.
Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
|
/linux/drivers/net/ethernet/intel/igb/ |
H A D | e1000_mbx.c | diff 9ce0e8d72678b5b60c99ce4c7af15ec127c761cb Sat Dec 12 01:45:38 CET 2015 Mitch Williams <mitch.a.williams@intel.com> igb/igbvf: don't give up
The driver shouldn't just give up if it fails to get the hardware mailbox lock. This can happen in a situation where the PF-VF communication channel is heavily loaded and causes complete communications failure between the PF and VF drivers.
Add a counter and a delay. The driver will now retry ten times, waiting one millisecond between retries.
Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
|