e5f9e82291
It's now possible to specify a time to wait until a connection to the discovery controller and the NVM controllers it exposes is made. Whenever that time is exceeded, a callback is immediately executed. However, depending on the stage of the discovery process, we might need to wait a while before actually stopping it (e.g. because a controller attach is in progress). That means that a discovery service might be visible for a while after it timed out. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I2d01837b581e0fa24c8e777730d88d990c94b1d8 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12684 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| aer.sh | ||
| async_init.sh | ||
| bdevperf.sh | ||
| discovery.sh | ||
| dma.sh | ||
| failover.sh | ||
| fio.sh | ||
| identify_kernel_nvmf.sh | ||
| identify.sh | ||
| multicontroller.sh | ||
| multipath.sh | ||
| perf.sh | ||
| target_disconnect.sh | ||