summaryrefslogtreecommitdiffstats
path: root/drivers/ide/qd65xx.c
diff options
context:
space:
mode:
authorSudheer Mogilappagari <sudheer.mogilappagari@intel.com>2017-12-18 05:17:25 -0500
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2018-01-23 11:29:19 -0800
commit07d44190a38939adfec6177a6e1b683417da291f (patch)
treebac8333644195b72c7208c447b75f4a69dd65229 /drivers/ide/qd65xx.c
parentd95cd48060e69d7135e65e667777ab7ddb1c9846 (diff)
downloadtalos-obmc-linux-07d44190a38939adfec6177a6e1b683417da291f.tar.gz
talos-obmc-linux-07d44190a38939adfec6177a6e1b683417da291f.zip
i40e/i40evf: Detect and recover hung queue scenario
In VFs, there is a known issue which can cause writebacks to not occur when interrupts are disabled and there are less than 4 descriptors resulting in TX timeout. Timeout can also occur due to lost interrupt. The current implementation for detecting and recovering from hung queues in the PF is problematic because it actually actively encourages lost interrupts. By triggering a SW interrupt, interrupts are forced on. If we are already in napi_poll and an interrupt fires, napi_poll will not be rescheduled and the interrupt is effectively lost; thereby potentially *causing* hung queues. This patch checks whether packets are being processed between every watchdog cycle and determine potential hung queue and fires triggers SW interrupt only for that particular queue. Signed-off-by: Sudheer Mogilappagari <sudheer.mogilappagari@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/ide/qd65xx.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud