b9af5dd834
Previously, when additional resets were submitted while a reset was in progress, those resets were queued and then executed serially as part of executing the original reset. Doing multiple resets on a bdev in quick succession is not useful if the first reset succeeds and is very unlikely to be useful in the negative case. Instead, we should batch resets and complete them all at once when the current reset succeeds or fails. Change-Id: If10e0f37526860eaeeb41a8803d6298a3eff3212 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/474599 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> |
||
|---|---|---|
| .. | ||
| bdev_internal.h | ||
| bdev_rpc.c | ||
| bdev_zone.c | ||
| bdev.c | ||
| Makefile | ||
| part.c | ||
| scsi_nvme.c | ||
| vtune.c | ||