1. 18 4月, 2018 1 次提交
  2. 27 3月, 2018 1 次提交
  3. 12 3月, 2018 1 次提交
  4. 05 3月, 2018 1 次提交
  5. 24 1月, 2018 1 次提交
  6. 29 12月, 2017 1 次提交
  7. 03 11月, 2017 1 次提交
  8. 21 8月, 2017 1 次提交
  9. 15 8月, 2017 1 次提交
  10. 07 1月, 2017 1 次提交
  11. 09 12月, 2016 2 次提交
  12. 21 10月, 2016 1 次提交
    • J
      ethernet: use net core MTU range checking in more drivers · d894be57
      Jarod Wilson 提交于
      Somehow, I missed a healthy number of ethernet drivers in the last pass.
      Most of these drivers either were in need of an updated max_mtu to make
      jumbo frames possible to enable again. In a few cases, also setting a
      different min_mtu to match previous lower bounds. There are also a few
      drivers that had no upper bounds checking, so they're getting a brand new
      ETH_MAX_MTU that is identical to IP_MAX_MTU, but accessible by includes
      all ethernet and ethernet-like drivers all have already.
      
      acenic:
      - min_mtu = 0, max_mtu = 9000
      
      amazon/ena:
      - min_mtu = 128, max_mtu = adapter->max_mtu
      
      amd/xgbe:
      - min_mtu = 0, max_mtu = 9000
      
      sb1250:
      - min_mtu = 0, max_mtu = 1518
      
      cxgb3:
      - min_mtu = 81, max_mtu = 65535
      
      cxgb4:
      - min_mtu = 81, max_mtu = 9600
      
      cxgb4vf:
      - min_mtu = 81, max_mtu = 65535
      
      benet:
      - min_mtu = 256, max_mtu = 9000
      
      ibmveth:
      - min_mtu = 68, max_mtu = 65535
      
      ibmvnic:
      - min_mtu = adapter->min_mtu, max_mtu = adapter->max_mtu
      - remove now redundant ibmvnic_change_mtu
      
      jme:
      - min_mtu = 1280, max_mtu = 9202
      
      mv643xx_eth:
      - min_mtu = 64, max_mtu = 9500
      
      mlxsw:
      - min_mtu = 0, max_mtu = 65535
      - Basically bypassing the core checks, and instead relying on dynamic
        checks in the respective switch drivers' ndo_change_mtu functions
      
      ns83820:
      - min_mtu = 0
      - remove redundant ns83820_change_mtu, only checked for mtu > 1500
      
      netxen:
      - min_mtu = 0, max_mtu = 8000 (P2), max_mtu = 9600 (P3)
      
      qlge:
      - min_mtu = 1500, max_mtu = 9000
      - driver only supports setting mtu to 1500 or 9000, so the core check only
        rules out < 1500 and > 9000, qlge_change_mtu still needs to check that
        the value is 1500 or 9000
      
      qualcomm/emac:
      - min_mtu = 46, max_mtu = 9194
      
      xilinx_axienet:
      - min_mtu = 64, max_mtu = 9000
      
      Fixes: 61e84623 ("net: centralize net_device min/max MTU checking")
      CC: netdev@vger.kernel.org
      CC: Jes Sorensen <jes@trained-monkey.org>
      CC: Netanel Belgazal <netanel@annapurnalabs.com>
      CC: Tom Lendacky <thomas.lendacky@amd.com>
      CC: Santosh Raspatur <santosh@chelsio.com>
      CC: Hariprasad S <hariprasad@chelsio.com>
      CC: Sathya Perla <sathya.perla@broadcom.com>
      CC: Ajit Khaparde <ajit.khaparde@broadcom.com>
      CC: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
      CC: Somnath Kotur <somnath.kotur@broadcom.com>
      CC: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
      CC: John Allen <jallen@linux.vnet.ibm.com>
      CC: Guo-Fu Tseng <cooldavid@cooldavid.org>
      CC: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
      CC: Jiri Pirko <jiri@mellanox.com>
      CC: Ido Schimmel <idosch@mellanox.com>
      CC: Manish Chopra <manish.chopra@qlogic.com>
      CC: Sony Chacko <sony.chacko@qlogic.com>
      CC: Rajesh Borundia <rajesh.borundia@qlogic.com>
      CC: Timur Tabi <timur@codeaurora.org>
      CC: Anirudha Sarangi <anirudh@xilinx.com>
      CC: John Linn <John.Linn@xilinx.com>
      Signed-off-by: NJarod Wilson <jarod@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d894be57
  13. 29 8月, 2016 1 次提交
  14. 15 8月, 2016 1 次提交
  15. 26 7月, 2016 1 次提交
  16. 26 6月, 2016 1 次提交
    • H
      cxgb4vf: Synchronize access to mailbox · b38066da
      Hariprasad Shenai 提交于
      The issue comes when there are multiple threads attempting to use the
      mailbox facility at the same time. The issue is the for the Virtual
      Function Driver, the only way to get the Virtual Interface statistics
      is to issue mailbox commands to ask the firmware for the VI Stats.
      And, because the VI Stats command can only retrieve a smallish number of
      stats per mailbox command, we have to issue three mailbox commands in quick
      succession. When ethtool or netstat command to get interface stats and
      interface up/down is run in a loop for every 0.1 sec, we observed
      mailbox collisions. And out of the two commands one would fail with
      the present code, since we don't queue the second command.
      
      To overcome the above issue, added a queue to access the mailbox.
      Whenever a mailbox command is issued add it to the queue. If its at the
      head issue the mailbox command, else wait for the existing command to
      complete. Usually command takes less than a milli-second to complete.
      Also timeout from the loop, if the command under execution takes
      long time to run.
      
      In reality, the number of mailbox access collisions is going to be very
      rare since no one runs such abusive script.
      Signed-off-by: NHariprasad Shenai <hariprasad@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b38066da
  17. 16 6月, 2016 1 次提交
  18. 30 4月, 2016 1 次提交
  19. 07 4月, 2016 1 次提交
  20. 11 3月, 2016 4 次提交
  21. 03 3月, 2016 2 次提交
  22. 19 2月, 2016 1 次提交
  23. 22 10月, 2015 1 次提交
  24. 13 5月, 2015 1 次提交
  25. 20 3月, 2015 1 次提交
  26. 15 1月, 2015 1 次提交
  27. 13 1月, 2015 2 次提交
  28. 06 1月, 2015 3 次提交
  29. 23 12月, 2014 1 次提交
  30. 10 12月, 2014 2 次提交
  31. 26 11月, 2014 1 次提交
    • H
      cxgb4/cxgb4vf/csiostor: Add T4/T5 PCI ID Table · 3fedeab1
      Hariprasad Shenai 提交于
      Add a new file t4_pci_id_tbl.h that contains T4/T5 PCI ID Table so that for all
      drivers that uses T4/T5 PCI functions changes can be done in one place.
      
      checkpatch.pl script reports following error, which if tried to fix ends up in
      compilation error.
      
      	ERROR: Macros with complex values should be enclosed in parentheses
      	+#define CH_PCI_DEVICE_ID_TABLE_DEFINE_END \
      	+		{ 0, } \
      	+	}
      
      	WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
      	new file mode 100644
      
      	ERROR: Macros with complex values should be enclosed in parentheses
      	+#define CH_PCI_ID_TABLE_FENTRY(devid) \
      	+	CH_PCI_ID_TABLE_ENTRY((devid) | \
      	+			      ((CH_PCI_DEVICE_ID_FUNCTION) << 8)), \
      	+	CH_PCI_ID_TABLE_ENTRY((devid) | \
      	+			      ((CH_PCI_DEVICE_ID_FUNCTION2) << 8))
      
      	ERROR: Macros with complex values should be enclosed in parentheses
      	+#define CH_PCI_DEVICE_ID_TABLE_DEFINE_END { 0, } }
      
      	ERROR: Macros with complex values should be enclosed in parentheses
      	+#define CH_PCI_DEVICE_ID_TABLE_DEFINE_END { 0, } }
      Signed-off-by: NHariprasad Shenai <hariprasad@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3fedeab1