+53
−7
Loading
A full controller reset sequence disconnects qpairs sequentially, but connects qpairs in parallel. It moves to the next ctrlr_channel after starting connection establishment for the previous ctrlr_channel. Conneciton establishment for qpairs are done in parallel. However, this design caused one very difficult race issue. As highlighted in the previous patch, a full controller reset sequence returned success but connection establishment was failed. It will be better if we confirm connection establishment one by one and return success after all connection establishments are actually done. Controller reset sequence does not require performance. This will reduce resource contention for connection establishment on the target side. Signed-off-by:Shuhei Matsumoto <smatsumoto@nvidia.com> Change-Id: Ifa2836f06865bcce6bc528719a51119522c8f43b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/18252 Reviewed-by:
Aleksey Marchuk <alexeymar@nvidia.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by:
Jim Harris <james.r.harris@intel.com>