| commit | 875328e4bce696e85edcda3c4b0ec80fd525e3a3 | |
| author | Jacob Keller <jacob.e.keller@intel.com> | |
| Fri, 16 Oct 2015 17:56:59 +0000 (16 10:56 -0700) | ||
| committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | |
| Sun, 6 Dec 2015 07:55:16 +0000 (5 23:55 -0800) | ||
| tree | 24caa1cce59a837c0df0991ef8b18f39a3afb711 | treesnapshot (tar.gz zip) |
| parent | 1343c65f70ee1b1f968a08b30e1836a4e37116cd | commitdiff |
fm10k: reinitialize queuing scheme after calling init_hw
The init_hw function may fail, and in the case of VFs, it might change
the number of maximum queues available. Thus, for every flow which
checks init_hw, we need to ensure that we clear the queue scheme before,
and initialize it after. The fm10k_io_slot_reset path will end up
triggering a reset so fm10k_reinit needs this change. The
fm10k_io_error_detected and fm10k_io_resume also need to properly clear
and reinitialize the queue scheme.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Bruce Allan <bruce.w.allan@intel.com>
Tested-by: Krishneil Singh <Krishneil.k.singh@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
The init_hw function may fail, and in the case of VFs, it might change
the number of maximum queues available. Thus, for every flow which
checks init_hw, we need to ensure that we clear the queue scheme before,
and initialize it after. The fm10k_io_slot_reset path will end up
triggering a reset so fm10k_reinit needs this change. The
fm10k_io_error_detected and fm10k_io_resume also need to properly clear
and reinitialize the queue scheme.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Bruce Allan <bruce.w.allan@intel.com>
Tested-by: Krishneil Singh <Krishneil.k.singh@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
| drivers/net/ethernet/intel/fm10k/fm10k_pci.c | diffblobblamehistory |