Target/iser: Fix initiator_depth and responder_resources
authorSagi Grimberg <sagig@mellanox.com>
Thu, 19 Jun 2014 10:54:19 +0000 (13:54 +0300)
committerNicholas Bellinger <nab@linux-iscsi.org>
Mon, 15 Sep 2014 21:02:55 +0000 (14:02 -0700)
commit1a92e17e39b9a5d476e0a7aa52280e76321834ee
tree71283d2eb8964a32803ab5fa932bc367d9c70ef3
parent38a8316b5d80ddee071d493bae567185c07de359
Target/iser: Fix initiator_depth and responder_resources

The iser target is the RDMA requester and the iser initiator is the
RDMA responder. In order to determine the max inflight RDMA READ requests
to set on the QP (initiator_depth), it should take the min between the
initiator published initiator_depth and the max inflight rdma read
requests its local HCA support (max_qp_init_rd_atom).

The target will never handle incoming RDMA READ requests so no need to
set responder_resources.

Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
drivers/infiniband/ulp/isert/ib_isert.c