d22497a72c
The recent refactoring removed the destruct poller and change the reset processing to destruct ctrlr after its completion by conditionally sending message. But differentiating callback function is difficult if we reset multiple ctrlrs. If nvme_bdev_ctrlr->destruct is set, any new reset cannot start. So we can use an new variable and always execute the callback function. Add an new variable pending_destruct to struct nvme_bdev_ctrlr, and set pending_destruct if ctrlr->ref is zero and ctrlr->destruct is true, and then start destruct ctrlr if ctrlr->destruct_after_reset is set after clearing pending resets. Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Change-Id: I9f34c42a40c5a5da54611e7871aef8c58117a56a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6714 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> |
||
|---|---|---|
| .. | ||
| accel | ||
| bdev | ||
| blob | ||
| blobfs | ||
| env_dpdk | ||
| event | ||
| sock | ||
| Makefile | ||