1. 25 1月, 2015 1 次提交
  2. 09 1月, 2013 1 次提交
  3. 08 12月, 2012 1 次提交
  4. 24 8月, 2012 1 次提交
  5. 11 7月, 2012 1 次提交
  6. 11 8月, 2011 1 次提交
  7. 28 6月, 2011 1 次提交
  8. 31 3月, 2011 1 次提交
  9. 21 12月, 2010 1 次提交
  10. 02 11月, 2010 1 次提交
  11. 21 10月, 2010 1 次提交
  12. 14 9月, 2010 1 次提交
  13. 04 9月, 2010 2 次提交
  14. 22 7月, 2010 1 次提交
  15. 25 2月, 2010 1 次提交
    • S
      RDMA/cxgb3: Doorbell overflow avoidance and recovery · e998f245
      Steve Wise 提交于
      T3 hardware doorbell FIFO overflows can cause application stalls due
      to lost doorbell ring events.  This has been seen when running large
      NP IMB alltoall MPI jobs.  The T3 hardware supports an xon/xoff-type
      flow control mechanism to help avoid overflowing the HW doorbell FIFO.
      
      This patch uses these interrupts to disable RDMA QP doorbell rings
      when we near an overflow condition, and then turn them back on (and
      ring all the active QP doorbells) when when the doorbell FIFO empties
      out.  In addition if an doorbell ring is dropped by the hardware, the
      code will now recover.
      
      Design:
      
      cxgb3:
      - enable these DB interrupts
      - in the interrupt handler, schedule work tasks to call the ULPs event
        handlers with the new events.
      - ring all the qset txqs when an overflow is detected.
      
      iw_cxgb3:
      - disable db ringing on all active qps when we get the DB_FULL event
      - enable db ringing on all active qps and ring all active dbs when we get
        the DB_EMPTY event
      - On DB_DROP event:
             - disable db rings in the event handler
             - delay-schedule a work task which rings and enables the dbs on
               all active qps.
      - in post_send and post_recv logic, don't ring the db if it's disabled.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      e998f245
  16. 16 2月, 2010 1 次提交
    • D
      cxgb3: fix link flap · e9449d85
      Divy Le Ray 提交于
      The driver is expected to report that the link is up
      when the phy Rx signal is established and the mac
      has not detected a link fault.
      The code is however broken, the driver does not check the link fault
      status when the phy link status changes.
      The link fault status being checked within a short period of time,
      it leads to link up/link down events.
      Signed-off-by: NDivy Le Ray <divy@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e9449d85
  17. 06 8月, 2009 1 次提交
  18. 03 8月, 2009 1 次提交
  19. 09 7月, 2009 1 次提交
  20. 30 5月, 2009 2 次提交
  21. 29 5月, 2009 1 次提交
  22. 21 5月, 2009 2 次提交
  23. 02 5月, 2009 1 次提交
  24. 30 4月, 2009 1 次提交
  25. 20 4月, 2009 1 次提交
  26. 27 3月, 2009 2 次提交
  27. 14 3月, 2009 2 次提交
  28. 19 2月, 2009 1 次提交
  29. 16 12月, 2008 1 次提交
  30. 11 11月, 2008 1 次提交
  31. 14 10月, 2008 1 次提交
  32. 09 10月, 2008 4 次提交