Skip to content
Snippets Groups Projects
  1. Mar 31, 2011
  2. Dec 21, 2010
  3. Nov 01, 2010
  4. Oct 21, 2010
  5. Sep 13, 2010
  6. Sep 03, 2010
  7. Jul 21, 2010
  8. Feb 24, 2010
    • Steve Wise's avatar
      RDMA/cxgb3: Doorbell overflow avoidance and recovery · e998f245
      Steve Wise authored
      
      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: default avatarSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: default avatarRoland Dreier <rolandd@cisco.com>
      e998f245
  9. Feb 15, 2010
    • Divy Le Ray's avatar
      cxgb3: fix link flap · e9449d85
      Divy Le Ray authored
      
      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: default avatarDivy Le Ray <divy@chelsio.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e9449d85
  10. Aug 05, 2009
  11. Aug 02, 2009
  12. Jul 08, 2009
  13. May 29, 2009
  14. May 20, 2009
  15. May 01, 2009
  16. Apr 29, 2009
  17. Apr 20, 2009
  18. Mar 27, 2009
  19. Mar 13, 2009
  20. Feb 18, 2009
  21. Dec 16, 2008
  22. Nov 11, 2008
  23. Oct 13, 2008
  24. Oct 08, 2008
  25. Jul 29, 2008
  26. Jul 10, 2008
  27. May 12, 2008
  28. Feb 03, 2008
Loading