95d8e7a683
"bdev_register" notification was sent right when register happened, which was misleading for any listener. Action on the registered bdev might not have been possible when examine took longer time. Order of bdev_register notifications in json_config test was modified, because they are being sent out as pollers for the spdk_bdev_wait_for_examine() are being processed. This is only because pollers are inserted at the tail, and processed from the tail as well. Order of notifications should not matter, as long as bdevs are ready for use. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I45b769f184b386df2daa4152ee766636ef0668ad Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5213 Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
---|---|---|
.. | ||
bdev_internal.h | ||
bdev_rpc.c | ||
bdev_zone.c | ||
bdev.c | ||
Makefile | ||
part.c | ||
scsi_nvme.c | ||
spdk_bdev.map | ||
vtune.c |