summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorBjørn Mork <bjorn@mork.no>2014-05-16 21:48:22 +0200
committerDavid S. Miller <davem@davemloft.net>2014-05-16 22:39:01 -0400
commit6c4e548ff36672eeb78f8288a2920d66fa4a6a66 (patch)
treefe2e6d17ffd63d02ee28d3a51e8a0b166ba1d311 /fs
parent68864abf08f06d7cbbabd03740beb383ccf5e5d5 (diff)
downloadlwn-6c4e548ff36672eeb78f8288a2920d66fa4a6a66.tar.gz
lwn-6c4e548ff36672eeb78f8288a2920d66fa4a6a66.zip
net: cdc_ncm: use ethtool to tune coalescing settings
Datagram coalescing is an integral part of the NCM and MBIM protocols, intended to reduce the interrupt load primarily on the device end of the USB link. As with all coalescing solutions, there is a trade-off between buffering and interrupts. The current defaults are based on the assumption that device side buffers should be the limiting factor. However, many modern high speed LTE modems suffers from buffer-bloat, making this assumption fail. This results in sub-optimal performance due to excessive coalescing. And in cases where such modems are connected to cheap embedded hosts there is often severe buffer allocation issues, giving very noticeable performance degradation . A start on improving this is going from build time hard coded limits to per device user configurable limits. The ethtool coalescing API was selected as user interface because, although the tuned values are buffer sizes, these settings directly control datagram coalescing. Signed-off-by: Bjørn Mork <bjorn@mork.no> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions