1. 13 2月, 2010 2 次提交
    • M
      tg3: Unwedge stuck MSI-X vectors · f89f38b8
      Matt Carlson 提交于
      The previous patch changed the code so that new rx buffer submissions to
      the hardware stall if a new submission would overwrite data needed by an
      unserviced rx packet.  On very busy 5717 and 57765 asic rev devices,
      there is a corner case where the hardware will fail to assert an MSI-X
      interrupt for rx traffic.  If that vector's interrupt never has another
      reason to assert, any rx buffers held will never be serviced.  If the
      buffers are never serviced and the hardware consumes all the available
      rx packets for other rx rings, deadlock will result.
      
      The most reliable and least intrusive way to work around the problem is
      to detect the case where new submissions would overwrite existing data
      and force all rx interrupt vectors to fire.
      Signed-off-by: NMatt Carlson <mcarlson@broadcom.com>
      Reviewed-by: NMichael Chan <mchan@broadcom.com>
      Reviewed-by: NBenjamin Li <benli@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f89f38b8
    • M
      tg3: Give MSI-X vec 1 rx backlog space · e4af1af9
      Matt Carlson 提交于
      RSS ring 1 is responsible for submitting new rx buffers to the
      hardware on behalf of all the other RSS rx return rings.  Up until now
      this ring submitted its new rx buffers to the producer ring directly.
      The following patch will require that this ring have a place to put
      backlogged rx packets.  As a consequence, it can no longer submit new
      buffers to the producer ring.
      
      This patch adds code to allocate an extra shadow producer ring for this
      RSS ring and adds RSS ring 1 to the list of rings needing buffer
      transfers.
      Signed-off-by: NMatt Carlson <mcarlson@broadcom.com>
      Signed-off-by: NMichael Chan <mchan@broadcom.com>
      Reviewed-by: NBenjamin Li <benli@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e4af1af9
  2. 21 1月, 2010 4 次提交
  3. 14 1月, 2010 2 次提交
  4. 04 12月, 2009 3 次提交
  5. 03 12月, 2009 1 次提交
  6. 16 11月, 2009 10 次提交
  7. 03 11月, 2009 8 次提交
  8. 07 10月, 2009 1 次提交
  9. 02 10月, 2009 1 次提交
  10. 02 9月, 2009 8 次提交