aboutsummaryrefslogtreecommitdiffstats
path: root/tools/bpf/bpftool/prog.c
diff options
context:
space:
mode:
authorBrett Creeley <[email protected]>2020-05-16 00:55:04 +0000
committerJeff Kirsher <[email protected]>2020-05-31 10:56:40 +0000
commita039f6fcba452fba5973798f4c641eee1ef770a1 (patch)
treeb745a7289e9da944e957434aea36b5928384dc16 /tools/bpf/bpftool/prog.c
parentice: fix PCI device serial number to be lowercase values (diff)
downloadkernel-a039f6fcba452fba5973798f4c641eee1ef770a1.tar.gz
kernel-a039f6fcba452fba5973798f4c641eee1ef770a1.zip
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 <[email protected]> Tested-by: Andrew Bowers <[email protected]> Signed-off-by: Jeff Kirsher <[email protected]>
Diffstat (limited to 'tools/bpf/bpftool/prog.c')
0 files changed, 0 insertions, 0 deletions