1. 01 1月, 2014 1 次提交
  2. 13 11月, 2013 1 次提交
  3. 06 9月, 2013 1 次提交
  4. 02 8月, 2013 1 次提交
    • Y
      bnx2x: Revising locking scheme for MAC configuration · 8b09be5f
      Yuval Mintz 提交于
      On very rare occasions, repeated load/unload stress test in the presence of
      our storage driver (bnx2i/bnx2fc) causes a kernel panic in bnx2x code
      (NULL pointer dereference). Stack traces indicate the issue happens during MAC
      configuration; thorough code review showed that indeed several races exist
      in which one thread can iterate over the list of configured MACs while another
      deletes entries from the same list.
      
      This patch adds a varient on the single-writer/Multiple-reader lock mechanism -
      It utilizes an already exsiting bottom-half lock, using it so that Whenever
      a writer is unable to continue due to the existence of another writer/reader,
      it pends its request for future deliverance.
      The writer / last readers will check for the existence of such requests and
      perform them instead of the original initiator.
      This prevents the writer from having to sleep while waiting for the lock
      to be accessible, which might cause deadlocks given the locks already
      held by the writer.
      
      Another result of this patch is that setting of Rx Mode is now made in
      sleepable context - Setting of Rx Mode is made under a bottom-half lock, which
      was always nontrivial for the bnx2x driver, as the HW/FW configuration requires
      wait for completions.
      Since sleep was impossible (due to the sleepless-context), various mechanisms
      were utilized to prevent the calling thread from sleep, but the truth was that
      when the caller thread (i.e, the one calling ndo_set_rx_mode()) returned, the
      Rx mode was still not set in HW/FW.
      
      bnx2x_set_rx_mode() will now overtly schedule for the Rx changes to be
      configured by the sp_rtnl_task which hold the RTNL lock and is sleepable
      context.
      Signed-off-by: NYuval Mintz <yuvalmin@broadcom.com>
      Signed-off-by: NAriel Elior <ariele@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8b09be5f
  5. 03 6月, 2013 2 次提交
  6. 22 3月, 2013 1 次提交
  7. 19 3月, 2013 1 次提交
  8. 12 3月, 2013 3 次提交
  9. 24 1月, 2013 5 次提交
  10. 16 1月, 2013 1 次提交
  11. 02 1月, 2013 1 次提交
    • A
      bnx2x: Support statistics collection for VFs by the PF · 67c431a5
      Ariel Elior 提交于
      Statistics are collected by the PF driver. The collection is
      performed via a query sent to the device which is basically an array
      of 3-tuples of the form (statistics client, function, DMAE address).
      In this patch the PF driver adds to the query, on top of the
      statistics clients it is maintaining for itself (rss queues, storage,
      etc), the 3-tuples for the VFs it is maintaining. The addresses used
      are the GPAs of the statistics buffers supplied by the VF in the
      init message on the VF <-> PF channel. The function parameter
      ensures that the iommu will translate the GPA to the correct physical
      address.
      Signed-off-by: NAriel Elior <ariele@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      67c431a5
  12. 19 11月, 2012 1 次提交
  13. 08 11月, 2012 1 次提交
  14. 17 10月, 2012 1 次提交
  15. 02 10月, 2012 1 次提交
  16. 06 9月, 2012 1 次提交
  17. 02 8月, 2012 1 次提交
  18. 20 6月, 2012 1 次提交
  19. 24 4月, 2012 1 次提交
    • B
      bnx2x: add afex support · a3348722
      Barak Witkowski 提交于
      Following patch adds afex multifunction support to the driver (afex
      multifunction is based on vntag header) and updates FW version used to 7.2.51.
      
      Support includes the following:
      
      1. Configure vif parameters in firmware (default vlan, vif id, default
         priority, allowed priorities) according to values received from NIC.
      2. Configure FW to strip/add default vlan according to afex vlan mode.
      3. Notify link up to OS only after vif is fully initialized.
      4. Support vif list set/get requests and configure FW accordingly.
      5. Supply afex statistics upon request from NIC.
      6. Special handling to L2 interface in case of FCoE vif.
      Signed-off-by: NBarak Witkowski <barak@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a3348722
  20. 04 4月, 2012 1 次提交
  21. 28 3月, 2012 1 次提交
  22. 20 3月, 2012 1 次提交
  23. 13 3月, 2012 5 次提交
  24. 21 2月, 2012 1 次提交
    • D
      use FW 7.2.16 · 621b4d66
      Dmitry Kravkov 提交于
      The patch integrates FW 7.2.16 HSI and implements driver
      part of GRO flow.
      
      FW 7.2.16 adds the ability to aggregate packets for GRO
      (and not just LRO) and also fixes some bugs.
      
      1. Added new aggregation mode: GRO. In this mode packets are aggregated
         such that the original packets can be reconstructed by the OS.
      2. 57712 HW bug workaround - initialized all CAM TM registers to 0x32.
      3. Adding the FCoE statistics structures to the BNX2X HSI.
      4. Wrong configuration of TX HW input buffer size may cause theoretical
         performance effect. Performed configuration fix.
      5. FCOE - Arrival of packets beyond task IO size can lead to crash.
         Fix firmware data-in flow.
      6. iSCSI - In rare cases of on-chip termination the graceful termination
         timer hangs, and the termination doesn't complete. Firmware fix to MSL
         timer tolerance.
      7. iSCSI - Chip hangs when target sends FIN out-of-order or with isles
         open at the initiator side. Firmware implementation corrected to drop
         FIN received out-of-order or with isles still open.
      8. iSCSI - Chip hangs when in case of retransmission not aligned to 4-bytes
         from the beginning of iSCSI PDU. Firmware implementation corrected
         to support arbitrary aligned retransmissions.
      9. iSCSI - Arrival of target-initiated NOP-IN during intense ISCSI traffic
         might lead to crash. Firmware fix to relevant flow.
      Signed-off-by: NDmitry Kravkov <dmitry@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      621b4d66
  25. 27 1月, 2012 1 次提交
  26. 26 1月, 2012 1 次提交
  27. 24 1月, 2012 1 次提交
  28. 07 12月, 2011 1 次提交
  29. 04 12月, 2011 1 次提交