setting responder_resources and initiator_depth

setting responder_resources and initiator_depth

[Andy Grover]

Hi all,

Currently, the RDS code sets both of these to 1 when calling
rdma_accept(). Using an arbitrary greater value (e.g. 64) doesn't seem
to work right.

I can call ib_query_qp(). Am I to assume I can set initiator_depth up to
ib_qp_attr.max_rd_atomic, and responder_resources to
ib_qp_attr.max_dest_rd_atomic and this will work?

Thanks -- Regards -- Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: setting responder_resources and initiator_depth

[Sean Hefty]

>Currently, the RDS code sets both of these to 1 when calling
>rdma_accept(). Using an arbitrary greater value (e.g. 64) doesn't seem
>to work right.
>
>I can call ib_query_qp(). Am I to assume I can set initiator_depth up to
>ib_qp_attr.max_rd_atomic, and responder_resources to
>ib_qp_attr.max_dest_rd_atomic and this will work?

You need to coordinate the values with those supported by the remote end of the
connection.  See the rdma_connect and rdma_accept man pages for additional
details.  The librdmacm has checks in rdma_connect and rdma_accept to verify
that the values provided by the user at least make sense for the local HW.

- Sean

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html