Skip to contentSkip to conversation

setting responder_resources and initiator_depth

DISCUSSION Andy Grover 2 participants 2 messages Jan 11, 2010 1 message not in the archive InfiniBand

lore
Share & tools
lore
#0 lore raw

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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 7 lines

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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html