From 94494579ce34200440d13c7c1ed06e7462deace3 Mon Sep 17 00:00:00 2001 From: Alexey Marchuk Date: Tue, 22 Feb 2022 12:39:34 +0300 Subject: [PATCH] nvme_rdma: Update reportring of RDMA responder resources responder_resources parameter of rdma cm tells remote side how many outstaing RDMA_READ of atomic operations local side can handle. Previously it was adjusted on queue depth but that was not correct since these parameters do not depend on each other. Even with qdepth=1 remote side may send several RDMA_READ operations per 1 IO request. With this change we report responder_resources equal to the maximum supported by RDMA device. Linux kernel nvme rdma driver reports this value in the same way. Signed-off-by: Alexey Marchuk Change-Id: I77e5c2ead6269da44c32a75a9188429f50d32ae4 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11698 Tested-by: SPDK CI Jenkins Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto Reviewed-by: Jim Harris --- lib/nvme/nvme_rdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/nvme/nvme_rdma.c b/lib/nvme/nvme_rdma.c index 2bdfc141e..82052e863 100644 --- a/lib/nvme/nvme_rdma.c +++ b/lib/nvme/nvme_rdma.c @@ -1134,7 +1134,7 @@ nvme_rdma_connect(struct nvme_rdma_qpair *rqpair) return ret; } - param.responder_resources = spdk_min(rqpair->num_entries, attr.max_qp_rd_atom); + param.responder_resources = attr.max_qp_rd_atom; ctrlr = rqpair->qpair.ctrlr; if (!ctrlr) {