summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/intel/i40evf/i40e_txrx.c
diff options
context:
space:
mode:
authorJacob Keller <jacob.e.keller@intel.com>2017-07-14 09:10:10 -0400
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2017-08-27 16:09:03 -0700
commit759dc4a7e605e0dc21708b0a6e0816ed0ac82641 (patch)
treeb4184ae7eed8c240d95ebae1f63b8100f1c3501a /drivers/net/ethernet/intel/i40evf/i40e_txrx.c
parent9254c0e34e4253c41fdcd4670b754506ce20d3eb (diff)
downloadlinux-0-day-759dc4a7e605e0dc21708b0a6e0816ed0ac82641.tar.gz
linux-0-day-759dc4a7e605e0dc21708b0a6e0816ed0ac82641.tar.xz
i40e: initialize our affinity_mask based on cpu_possible_mask
On older kernels a call to irq_set_affinity_hint does not guarantee that the IRQ affinity will be set. If nothing else on the system sets the IRQ affinity this can result in a bug in the i40e_napi_poll() routine where we notice that our interrupt fired on the "wrong" CPU according to our internal affinity_mask variable. This results in a bug where we continuously tell NAPI to stop polling to move the interrupt to a new CPU, but the CPU never changes because our affinity mask does not match the actual mask setup for the IRQ. The root problem is a mismatched affinity mask value. So lets initialize the value to cpu_possible_mask instead. This ensures that prior to the first time we get an IRQ affinity notification we'll have the mask set to include every possible CPU. We use cpu_possible_mask instead of cpu_online_mask since the former is almost certainly never going to change, while the later might change after we've made a copy. Signed-off-by: Jacob Keller <jacob.e.keller@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/net/ethernet/intel/i40evf/i40e_txrx.c')
0 files changed, 0 insertions, 0 deletions