Jim Harris 6c61e733a2 nvme: allocate extra request for fabrics connect ... With async connect, we need to avoid the case where the initiator is sending the icreq, and meanwhile the application submits enough I/O such that the request objects are exhausted, leaving none for the FABRICS/CONNECT command that we need to send after the icreq is done. So allocate an extra request, and then use it when sending the FABRICS/CONNECT command, rather than trying to pull one from the qpair's STAILQ. Fixes issue #2371. Signed-off-by: Jim Harris <james.r.harris@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11515 (master) (cherry picked from commit 635d0cbe75) Change-Id: If42a3fbb3fd9d863ee48cf5cae75a9ba1754c349 Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12469 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>		2022-06-30 13:32:31 -04:00
..
Makefile	test/nvme_fabric: build nvme fabric unittest file	2021-04-22 07:27:41 +00:00
nvme_fabric_ut.c	nvme: allocate extra request for fabrics connect	2022-06-30 13:32:31 -04:00