On 7/1/2015 7:30 PM, Steve Wise wrote:
Memory regions that are the target of an iWARP RDMA READ RESPONSE need
REMOTE_WRITE access rights.  So enable REMOTE_WRITE for iWARP devices.

Use the device's max_sge_rd capability to compute the target's read sge
depth.  Save both the read and write max_sge values in the isert_conn
struct, and use these when creating RDMA_READ work requests

Signed-off-by: Steve Wise <[email protected]>
---
  drivers/infiniband/ulp/isert/ib_isert.c |   54 ++++++++++++++++++++++++++-----
  drivers/infiniband/ulp/isert/ib_isert.h |    3 +-
  2 files changed, 47 insertions(+), 10 deletions(-)

diff --git a/drivers/infiniband/ulp/isert/ib_isert.c 
b/drivers/infiniband/ulp/isert/ib_isert.c
index 9e7b492..8334dd0 100644
--- a/drivers/infiniband/ulp/isert/ib_isert.c
+++ b/drivers/infiniband/ulp/isert/ib_isert.c
@@ -163,7 +163,9 @@ isert_create_qp(struct isert_conn *isert_conn,
         * outgoing control PDU responses.
         */
        attr.cap.max_send_sge = max(2, device->dev_attr.max_sge - 2);
-       isert_conn->max_sge = attr.cap.max_send_sge;
+       isert_conn->max_write_sge = attr.cap.max_send_sge;
+       isert_conn->max_read_sge = min_t(u32, device->dev_attr.max_sge_rd,
+                                        attr.cap.max_send_sge);

        attr.cap.max_recv_sge = 1;
        attr.sq_sig_type = IB_SIGNAL_REQ_WR;
@@ -348,6 +350,17 @@ out_cq:
        return ret;
  }

+static int any_port_is_iwarp(struct isert_device *device)
+{
+       int i;
+
+       for (i = rdma_start_port(device->ib_device);
+            i <= rdma_end_port(device->ib_device); i++)
+               if (rdma_protocol_iwarp(device->ib_device, i))
+                       return 1;
+       return 0;
+}
+

Lets get rid of that as soon as possible...

However,
Reviewed-by: Sagi Grimberg <[email protected]>


Nic,

I think it makes sense that this will go via doug's tree.
Any objection?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to