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 <alexeymar@mellanox.com> Change-Id: I77e5c2ead6269da44c32a75a9188429f50d32ae4 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11698 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
parent
bc72388eb6
commit
94494579ce
@ -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) {
|
||||
|
Loading…
Reference in New Issue
Block a user