summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorBrett Creeley <brett.creeley@intel.com>2020-05-16 03:55:04 +0300
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2020-05-31 13:56:40 +0300
commita039f6fcba452fba5973798f4c641eee1ef770a1 (patch)
treeb745a7289e9da944e957434aea36b5928384dc16 /tools/perf/scripts/python
parent1a9c561aa35534a03c0aa51c7fb1485731202a7c (diff)
downloadlinux-a039f6fcba452fba5973798f4c641eee1ef770a1.tar.xz
ice: Use coalesce values from q_vector 0 when increasing q_vectors
Currently when a VSI is built (i.e. reset, set channels, etc.) the coalesce settings will be preserved in most cases. However, when the number of q_vectors are increased the settings for the new q_vectors will be set to the driver defaults of AIM on, Rx/Tx ITR 50, and INTRL 0. This is causing issues with how the ethtool layer gets the current coalesce settings since it only uses q_vector 0. So, assume that the user set the coalesce settings globally (i.e. ethtool -C eth0) and use q_vector 0's settings for all of the new q_vectors. Signed-off-by: Brett Creeley <brett.creeley@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions