summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorBrett Creeley <brett.creeley@intel.com>2019-03-01 02:25:47 +0300
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2019-04-18 18:38:48 +0300
commit711987bbad18e6d5fc5d8ff07c8991700e2ed1b6 (patch)
treebaabd204980889bce5a760d5f65a29234364e80d /tools/perf/scripts/python/exported-sql-viewer.py
parent9c010de7cf0a76f22fb38800816d34cf95ff9002 (diff)
downloadlinux-711987bbad18e6d5fc5d8ff07c8991700e2ed1b6.tar.xz
ice: Calculate ITR increment based on direct calculation
Currently when calculating how much to increment ITR by inside of ice_update_itr() we do some estimations and intermediate calculations. Instead of doing estimations, just do the calculation directly. This allows for a more accurate value and it makes it easier for the next person to understand and update. Also, remove the dividing the ITR value by 2 when latency driven because the ITR values are already so low for 100Gbps speed. This should help get to the desired ITR value faster. Signed-off-by: Brett Creeley <brett.creeley@intel.com> Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@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/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions