+16
−19
Loading
When SRQ is supported, recv objects will be allocated by poll group and qpair will associated and use them. In this case, we do not want qpair to allocate and free recv objects. When connection is established, it will be decided if SRQ is used or not. Hence, defer recv objects allocation until connection is established. Send objects are not affected directly by SRQ, but nvme_rdma_register_reqs() no longer does any registration and deferring send objects allocation makes the code more consistent. Hence, defer send objects allocation until connection is established too. Even after this patch, we rely on nvme_rdma_ctrlr_delete_io_qpair() to free resources completely. Signed-off-by:Shuhei Matsumoto <smatsumoto@nvidia.com> Signed-off-by:
Denis Nagorny <denisn@nvidia.com> Signed-off-by:
Evgeniy Kochetov <evgeniik@nvidia.com> Change-Id: Ic151fad01009d92a7fc809a730e6e9dff1a365f3 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14169 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by:
Ben Walker <benjamin.walker@intel.com> Reviewed-by:
Aleksey Marchuk <alexeymar@nvidia.com>