diff options
| author | Alexander Duyck <alexander.h.duyck@linux.intel.com> | 2019-09-04 08:07:11 -0700 |
|---|---|---|
| committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2019-09-11 09:39:35 -0700 |
| commit | 377228accbbb8b9738f615d791aa803f41c067e0 (patch) | |
| tree | 4961261dba62bfed613f082afb01d9f9a524e8d9 /fs | |
| parent | f4b752a6b2708bfdf7fbe8a241082c8104f4ce05 (diff) | |
ixgbe: Prevent u8 wrapping of ITR value to something less than 10us
There were a couple cases where the ITR value generated via the adaptive
ITR scheme could exceed 126. This resulted in the value becoming either 0
or something less than 10. Switching back and forth between a value less
than 10 and a value greater than 10 can cause issues as certain hardware
features such as RSC to not function well when the ITR value has dropped
that low.
CC: stable@vger.kernel.org
Fixes: b4ded8327fea ("ixgbe: Update adaptive ITR algorithm")
Reported-by: Gregg Leventhal <gleventhal@janestreet.com>
Signed-off-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions