summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2018-03-30 10:03:37 -0400
committerDavid S. Miller <davem@davemloft.net>2018-03-30 10:03:37 -0400
commit95e623fd98d21a42528854f657910dfbbd768df8 (patch)
tree4b1ebeeac784369b3c7b9be808d0f72735fca711 /MAINTAINERS
parent9daae9bd47cff82a2a06aca23c458d6c79d09d52 (diff)
parent5e6ce1f1a4ca83878f2966dd67afb39b631c4320 (diff)
downloadlinux-95e623fd98d21a42528854f657910dfbbd768df8.tar.bz2
Merge branch 'net-Broadcom-drivers-coalescing-fixes'
Florian Fainelli says: ==================== net: Broadcom drivers coalescing fixes Following Tal's review of the adaptive RX/TX coalescing feature added to the SYSTEMPORT and GENET driver a number of things showed up: - adaptive TX coalescing is not actually a good idea with the current way the estimator will program the ring, this results in a higher CPU load, NAPI on TX already does a reasonably good job at maintaining the interrupt count low - both SYSTEMPORT and GENET would suffer from the same issues while configuring coalescing parameters where the values would just not be applied correctly based on user settings, so we fix that too Tal, thanks again for your feedback, I would appreciate if you could review that the new behavior appears to be implemented correctly. Thanks! Changes in v2: - added Tal's reviewed-by to the first patch - split DIM initialization from coalescing parameters initialization - avoid duplicating the same code in bcmgenet_set_coalesce() when configuring RX rings - fixed the condition where default DIM parameters would be applied when adaptive RX coalescing would be enabled, do this only if it was disabled before ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions