1. 24 5月, 2009 1 次提交
    • M
      [SCSI] iscsi: pass ep connect shost · 10eb0f01
      Mike Christie 提交于
      When we create the tcp/ip connection by calling ep_connect, we currently
      just go by the routing table info.
      
      I think there are two problems with this.
      
      1. Some drivers do not have access to a routing table. Some drivers like
      qla4xxx do not even know about other ports.
      
      2. If you have two initiator ports on the same subnet, the user may have
      set things up so that session1 was supposed to be run through port1. and
      session2 was supposed to be run through port2. It looks like we could
      end with both sessions going through one of the ports.
      
      Fixes for cxgb3i from Karen Xie.
      Signed-off-by: NMike Christie <michaelc@cs.wisc.edu>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      10eb0f01
  2. 27 4月, 2009 1 次提交
  3. 14 3月, 2009 5 次提交
  4. 28 2月, 2009 1 次提交
  5. 13 1月, 2009 1 次提交
    • R
      IB/iser: Add dependency on INFINIBAND_ADDR_TRANS · f5eb3b76
      Randy Dunlap 提交于
      Fix ib_iser build to depend on INFINIBAND_ADDR_TRANS; if INET=y but
      IPV6=n, then the RDMA CM is not built but INFINIBAND_ISER can be
      enabled, leading to:
      
          ERROR: "rdma_destroy_id" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
          ERROR: "rdma_connect" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
          ERROR: "rdma_destroy_qp" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
          ERROR: "rdma_create_id" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
          ERROR: "rdma_create_qp" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
          ERROR: "rdma_resolve_route" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
          ERROR: "rdma_disconnect" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
          ERROR: "rdma_resolve_addr" [drivers/infiniband/ulp/iser/ib_iser.ko] undefined!
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      f5eb3b76
  6. 30 12月, 2008 2 次提交
  7. 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
  8. 31 10月, 2008 1 次提交
  9. 13 10月, 2008 2 次提交
  10. 24 8月, 2008 1 次提交
  11. 23 7月, 2008 1 次提交
  12. 15 7月, 2008 1 次提交
  13. 12 7月, 2008 14 次提交
  14. 30 4月, 2008 2 次提交
  15. 17 4月, 2008 2 次提交
  16. 11 3月, 2008 2 次提交
  17. 26 1月, 2008 2 次提交