Skip to content

K
kernel_linux

OpenHarmony / kernel_linux
上一次同步 4 年多

通知 15
Star 8
Fork 2
K
kernel_linux
切换分支/标签
  1. 09 2月, 2013 1 次提交
  3. 05 2月, 2013 2 次提交
    • J
      drivers: net: usb: Remove unnecessary alloc/OOM messages · 38673c82
      由 Joe Perches 提交于 
      alloc failures already get standardized OOM
messages and a dump_stack.
Signed-off-by: NJoe Perches <joe@perches.com>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      38673c82
    • B
      net: usbnet: fix tx_dropped statistics · bf414b36
      由 Bjørn Mork 提交于 
      It is normal for minidrivers accumulating frames to return NULL
from their tx_fixup function. We do not want to count this as a
drop, or log any debug messages.  A different exit path is
therefore chosen for such drivers, skipping the debug message
and the tx_dropped increment.

The test for accumulating drivers was however completely bogus,
making the exit path selection depend on whether the user had
enabled tx_err logging or not. This would arbitrarily mess up
accounting for both accumulating and non-accumulating minidrivers,
and would result in unwanted debug messages for the accumulating
drivers.

Fix by testing for FLAG_MULTI_PACKET instead, which probably was
the intention from the beginning.  This usage match the documented
behaviour of this flag:

 Indicates to usbnet, that USB driver accumulates multiple IP packets.
 Affects statistic (counters) and short packet handling.
Signed-off-by: NBjørn Mork <bjorn@mork.no>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bf414b36
  5. 31 1月, 2013 2 次提交
  7. 28 1月, 2013 2 次提交
  9. 24 1月, 2013 1 次提交
    • B
      net: cdc_mbim: send ZLP only for the specific buggy device · 844e88f0
      由 Bjørn Mork 提交于 
      Reverting 328d7b8a and instead adding an exception for the
Sierra Wireless MC7710.

commit 328d7b8a (net: cdc_mbim: send ZLP after max sized NTBs)
added a workaround for an issue observed on one specific device.
Concerns were raised that this workaround adds a performance
penalty to all devices based on questionable, if not buggy,
behaviour of a single device:

 "If you add ZLP for NTBs of dwNtbOutMaxSize, you are heavily affecting CPU
  load, increasing interrupt load by factor of 2 in high load traffic
  scenario and possibly decreasing throughput for all other devices
  which behaves correctly."

 "The idea of NCM was to avoid extra ZLPs. If your transfer is exactly
  dwNtbOutMaxSize, it's known, you can submit such request on the receiver
  side and you do not need any EOT indicatation, so the frametime can be
  used for useful data."

Adding a device specific exception to prevent the workaround from
affecting well behaved devices.

The assumption here is that needing a ZLP is truly an *exception*.
We do not yet have enough data to verify this.  The generic
workaround in commit 328d7b8a should be considered acceptable despite
the performance penalty if the exception list becomes a maintainance
hassle.

Cc: Alexey ORISHKO <alexey.orishko@stericsson.com>
Cc: Yauheni Kaliuta <y.kaliuta@gmail.com>
Signed-off-by: NBjørn Mork <bjorn@mork.no>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      844e88f0
  11. 22 1月, 2013 5 次提交
  13. 21 1月, 2013 1 次提交
  15. 20 1月, 2013 1 次提交
  17. 19 1月, 2013 4 次提交
  19. 17 1月, 2013 2 次提交
  21. 15 1月, 2013 1 次提交
  23. 09 1月, 2013 1 次提交
  25. 07 1月, 2013 1 次提交
  27. 05 1月, 2013 2 次提交
  29. 29 12月, 2012 1 次提交
  31. 20 12月, 2012 4 次提交
  33. 18 12月, 2012 2 次提交
  35. 11 12月, 2012 3 次提交
  37. 01 12月, 2012 4 次提交