1. 18 3月, 2014 3 次提交
  2. 10 8月, 2013 6 次提交
  3. 05 6月, 2013 1 次提交
  4. 02 5月, 2013 3 次提交
  5. 22 2月, 2013 1 次提交
  6. 04 10月, 2012 1 次提交
  7. 06 3月, 2012 1 次提交
    • O
      IB/iser: Post initial receive buffers before sending the final login request · 89e984e2
      Or Gerlitz 提交于
      An iser target may send iscsi NO-OP PDUs as soon as it marks the iSER
      iSCSI session as fully operative.  This means that there is window
      where there are no posted receive buffers on the initiator side, so
      it's possible for the iSER RC connection to break because of RNR NAK /
      retry errors.  To fix this, rely on the flags bits in the login
      request to have FFP (0x3) in the lower nibble as a marker for the
      final login request, and post an initial chunk of receive buffers
      before sending that login request instead of after getting the login
      response.
      Signed-off-by: NOr Gerlitz <ogerlitz@mellanox.com>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NRoland Dreier <roland@purestorage.com>
      89e984e2
  8. 05 11月, 2011 2 次提交
  9. 18 8月, 2011 1 次提交
  10. 07 6月, 2011 1 次提交
  11. 31 3月, 2011 1 次提交
  12. 13 5月, 2010 2 次提交
    • O
      IB/iser: Enhance disconnection logic for multi-pathing · 39ff05db
      Or Gerlitz 提交于
      The iser connection teardown flow isn't over until the underlying
      Connection Manager (e.g the IB CM) delivers a disconnected or timeout
      event through the RDMA-CM.  When the remote (target) side isn't
      reachable, e.g when some HW e.g port/hca/switch isn't functioning or
      taken down administratively, the CM timeout flow is used and the event
      may be generated only after relatively long time -- on the order of
      tens of seconds.
      
      The current iser code exposes this possibly long delay to higher
      layers, specifically to the iscsid daemon and iscsi kernel stack. As a
      result, the iscsi stack doesn't respond well: this low-level CM delay
      is added to the fail-over time under HA schemes such as the one
      provided by DM multipath through the multipathd(8) service.
      
      This patch enhances the reference counting scheme on iser's IB
      connections so that the disconnect flow initiated by iscsid from user
      space (ep_disconnect) doesn't wait for the CM to deliver the
      disconnect/timeout event.  (The connection teardown isn't done from
      iser's view point until the event is delivered)
      
      The iser ib (rdma) connection object is destroyed when its reference
      count reaches zero.  When this happens on the RDMA-CM callback
      context, extra care is taken so that the RDMA-CM does the actual
      destroying of the associated ID, since doing it in the callback is
      prohibited.
      
      The reference count of iser ib connection normally reaches three,
      where the <ref, deref> relations are
      
       1. conn <init, terminate>
       2. conn <bind, stop/destroy>
       3. cma id <create, disconnect/error/timeout callbacks>
      
      With this patch, multipath fail-over time is about 30 seconds, while
      without this patch, multipath fail-over time is about 130 seconds.
      Signed-off-by: NOr Gerlitz <ogerlitz@voltaire.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      39ff05db
    • O
      IB/iser: Add asynchronous event handler · 2110f9bf
      Or Gerlitz 提交于
      Add handler to handle events such as port up and down.  This is useful
      when testing high-availability schemes such as multi-pathing.
      Signed-off-by: NOr Gerlitz <ogerlitz@voltaire.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      2110f9bf
  13. 25 2月, 2010 6 次提交
  14. 14 3月, 2009 1 次提交
  15. 22 12月, 2008 1 次提交
    • D
      IB/iser: Avoid recv buffer exhaustion caused by unexpected PDUs · bba7ebba
      David Disseldorp 提交于
      iSCSI/iSER targets may send PDUs without a prior request from the
      initiator.  RFC 5046 refers to these PDUs as "unexpected".  NOP-In PDUs
      with itt=RESERVED and Asynchronous Message PDUs occupy this category.
      
      The amount of active "unexpected" PDU's an iSER target may have at any
      time is governed by the MaxOutstandingUnexpectedPDUs key, which is not
      yet supported.
      
      Currently when an iSER target sends an "unexpected" PDU, the
      initiators recv buffer consumed by the PDU is not replaced.  If over
      initial_post_recv_bufs_num "unexpected" PDUs are received then the
      receive queue will run out of receive work requests entirely.
      
      This patch ensures recv buffers consumed by "unexpected" PDUs are
      replaced in the next iser_post_receive_control() call.
      Signed-off-by: NDavid Disseldorp <ddiss@sgi.com>
      Signed-off-by: NKen Sandars <ksandars@sgi.com>
      Acked-by: NOr Gerlitz <ogerlitz@voltaire.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      bba7ebba
  16. 15 7月, 2008 1 次提交
  17. 12 7月, 2008 6 次提交
  18. 30 4月, 2008 1 次提交
  19. 18 7月, 2007 1 次提交
    • R
      IB/iser: Make a couple of functions static · 41179e2d
      Roland Dreier 提交于
      Make iser_conn_release() and iser_start_rdma_unaligned_sg() static,
      since they are only used in the .c file where they are defined.  In
      addition to being a cleanup, this even shrinks the generated code by
      allowing the single call of iser_start_rdma_unaligned_sg() to be
      inlined into its callsite.  On x86_64:
      
      add/remove: 0/1 grow/shrink: 1/0 up/down: 466/-533 (-67)
      function                                     old     new   delta
      iser_reg_rdma_mem                           1518    1984    +466
      iser_start_rdma_unaligned_sg                 533       -    -533
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      41179e2d