+19
−4
Loading
For the following nvme controller statemachine states: NVME_CTRLR_STATE_IDENTIFY_NS NVME_CTRLR_STATE_IDENTIFY_ID_DESCS NVME_CTRLR_STATE_IDENTIFY_NS_IOCS_SPECIFIC The statemachine can either: - Jump to succeeding state - If active ns list is empty, jump directly to NVME_CTRLR_STATE_CONFIGURE_AER - In the unlikely case if NVMe completion error, jump to NVME_CTRLR_STATE_ERROR Simply this such that we either: - Jump to succeeding state - In the unlikely case if NVMe completion error, jump to NVME_CTRLR_STATE_ERROR This will help to reduce the complexity of the nvme controller statemachine, especially considering that there are new additional states (NVME_CTRLR_STATE_IDENTIFY_NS_DIRECTIVE and NVME_CTRLR_STATE_CONFIGURE_NS_STREAMS) currently on review that would continue with the bad habit of having three possible jump states instead of just two. Signed-off-by:Niklas Cassel <niklas.cassel@wdc.com> Change-Id: I3242052b1108afcd8adbe6d0378b1358fef58ec8 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6521 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by:
sunshihao <sunshihao@huawei.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com>