diff options
author | 2021-06-11 09:33:34 +0200 | |
---|---|---|
committer | 2021-06-11 12:49:15 -0700 | |
commit | 7a4b92e8e0de9cbbb623310af76b1d60cd344b1d (patch) | |
tree | ee81c598aeb2a729a03cc91c66e09a20e509e687 /drivers/vlynq | |
parent | s390/qeth: count TX completion interrupts (diff) | |
download | linux-7a4b92e8e0de9cbbb623310af76b1d60cd344b1d.tar.gz linux-7a4b92e8e0de9cbbb623310af76b1d60cd344b1d.tar.bz2 linux-7a4b92e8e0de9cbbb623310af76b1d60cd344b1d.zip |
s390/qeth: also use TX NAPI for non-IQD devices
Set scan_threshold = 0 to opt out from the qdio layer's internal tasklet
& timer mechanism for TX completions, and replace it with the TX NAPI
infrastructure that qeth already uses for IQD devices. This avoids the
fragile logic in qdio_check_output_queue(), enables tighter integration
and gives us more tuning options via ethtool in the future.
For now we continue to apply the same policy as the qdio layer:
scan for completions if 32 TX buffers are in use, or after 1 sec.
A re-scan is done after 10 sec, but only if no TX interrupt is pending.
With scan_threshold = 0 we no longer get TX completion scans from
within qdio_get_next_buffers(). So trigger these manually in qeth_poll()
and in the RX path switch to the equivalent qdio_inspect_queue().
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/vlynq')
0 files changed, 0 insertions, 0 deletions