nvme/rdma: Fix specification of R/W queue depth

The meaning of the parameters was swapped.

Change-Id: I3f4938c446fd06afd1852bcf08e779b7b988855d
Signed-off-by: Ben Walker <benjamin.walker@intel.com>
This commit is contained in:
Ben Walker 2016-12-15 13:53:11 -07:00 committed by Daniel Verkamp
parent 375da65762
commit b2a86421f4
2 changed files with 3 additions and 3 deletions

View File

@ -576,8 +576,8 @@ nvme_rdma_connect(struct nvme_rdma_qpair *rqpair)
specified here, but the other param values either zeroed out or
replaced.
*/
conn_param.responder_resources = 1; /* 0 or 1*/
conn_param.initiator_depth = nvme_min(rqpair->max_queue_depth, attr.max_qp_init_rd_atom);
conn_param.responder_resources = nvme_min(rqpair->max_queue_depth, attr.max_qp_rd_atom);
conn_param.initiator_depth = 0;
conn_param.retry_count = 7;
conn_param.rnr_retry_count = 7;

View File

@ -671,7 +671,7 @@ nvmf_rdma_connect(struct rdma_cm_event *event)
/* Next check the remote NIC's hardware limitations */
rdma_param = &event->param.conn;
SPDK_TRACELOG(SPDK_TRACE_RDMA,
"Host NIC Max Incoming RDMA R/W operations: %d Max Outgoing RDMA R/W operations: %d\n",
"Host (Initiator) NIC Max Incoming RDMA R/W operations: %d Max Outgoing RDMA R/W operations: %d\n",
rdma_param->initiator_depth, rdma_param->responder_resources);
if (rdma_param->initiator_depth > 0) {
max_rw_depth = nvmf_min(max_rw_depth, rdma_param->initiator_depth);