1. 29 Jun, 2017 8 commits
  2. 27 Jun, 2017 28 commits
  3. 25 Jun, 2017 4 commits
    • Michael Grzeschik's avatar
      net: macb: add fixed-link node support · dacdbb4d
      Michael Grzeschik authored
      In case the MACB is directly connected to a
      non-mdio PHY/device, it should be possible to provide
      a fixed link configuration in the DT.
      Signed-off-by: default avatarMichael Grzeschik <m.grzeschik@pengutronix.de>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      dacdbb4d
    • David S. Miller's avatar
      Merge tag 'wireless-drivers-next-for-davem-2017-06-25' of... · 24a72b77
      David S. Miller authored
      Merge tag 'wireless-drivers-next-for-davem-2017-06-25' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
      
      Kalle Valo says:
      
      ====================
      wireless-drivers-next patches for 4.13
      
      New features and bug fixes to quite a few different drivers, but
      nothing really special standing out.
      
      What makes me happy that we have now more vendors actively
      contributing to upstream drivers. In this pull request we have patches
      from Broadcom, Intel, Qualcomm, Realtek and Redpine Signals, and I
      still have patches from Marvell and Quantenna pending in patchwork. Now
      that's something comparing to how things looked 11 years ago in Jeff
      Garzik's "State of the Union: Wireless" email:
      
      https://lkml.org/lkml/2006/1/5/671
      
      Major changes:
      
      wil6210
      
      * add low level RF sector interface via nl80211 vendor commands
      
      * add module parameter ftm_mode to load separate firmware for factory
        testing
      
      * support devices with different PCIe bar size
      
      * add support for PCIe D3hot in system suspend
      
      * remove ioctl interface which should not be in a wireless driver
      
      ath10k
      
      * go back to using dma_alloc_coherent() for firmware scratch memory
      
      * add per chain RSSI reporting
      
      brcmfmac
      
      * add support multi-scheduled scan
      
      * add scheduled scan support for specified BSSIDs
      
      * add support for brcm43430 revision 0
      
      wlcore
      
      * add wil1285 compatible
      
      rsi
      
      * add RS9113 USB support
      
      iwlwifi
      
      * FW API documentation improvements (for tools and htmldoc)
      
      * continuing work for the new A000 family
      
      * bump the maximum supported FW API to 31
      
      * improve the differentiation between 8000, 9000 and A000 families
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      24a72b77
    • David S. Miller's avatar
      Merge branch 'sctp-RFC-4960-Errata-fixes' · ca7bbc84
      David S. Miller authored
      Marcelo Ricardo Leitner says:
      
      ====================
      sctp: RFC 4960 Errata fixes
      
      This patchset contains fixes for 4 Errata topics from
      https://tools.ietf.org/html/draft-ietf-tsvwg-rfc4960-errata-01
      Namely, sections:
       3.12. Order of Adjustments of partial_bytes_acked and cwnd
       3.22. Increase of partial_bytes_acked in Congestion Avoidance
       3.26. CWND Increase in Congestion Avoidance Phase
       3.27. Refresh of cwnd and ssthresh after Idle Period
      
      Tests performed with netperf using net namespaces, with drop rates at
      0%, 0.5% and 1% by netem, IPv4 and IPv6, 10 runs for each combination.
      I couldn't spot differences on the stats. With and without these patches
      the results vary in a similar way in terms of throughput and
      retransmissions.
      
      Tests with 20ms delay and 20ms delay + drops at 0.5% and 1% also had
      results in a similar way, no noticeable difference.
      
      Looking at cwnd, it was possible to notice slightly lower values being
      used while still sustaining same throughput profile.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ca7bbc84
    • Marcelo Ricardo Leitner's avatar
      sctp: adjust ssthresh when transport is idle · a02d036c
      Marcelo Ricardo Leitner authored
      RFC 4960 Errata 3.27 identifies that ssthresh should be adjusted to cwnd
      because otherwise it could cause the transport to lock into congestion
      avoidance phase specially if ssthresh was previously reduced by some
      packet drop, leading to poor performance.
      
      The Errata says to adjust ssthresh to cwnd only once, though the same
      goal is achieved by updating it every time we update cwnd too. The
      caveat is that we could take longer to get back up to speed but that
      should be compensated by the fact that we don't adjust on RTO basis (as
      RFC says) but based on Heartbeats, which are usually way longer.
      
      See-also: https://tools.ietf.org/html/draft-ietf-tsvwg-rfc4960-errata-01#section-3.27Signed-off-by: default avatarMarcelo Ricardo Leitner <marcelo.leitner@gmail.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      a02d036c