acf116c6d5
When we do detect new devices, we would like to get them attached as quickly as possible. Controller initialization requires a non-trivial number of admin commands, and when using async probe, it means that after we have detected a new device, it will take many iterations of calling spdk_nvme_probe_poll_async() before the controller is fully attached. So when we are actively probing a probe_ctx, create a new poller that is solely responsible for probing that context at a much higher frequency. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I72fbe3faef2d72608edb163bd87907902d7c3adc Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5646 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: Paul Luse <paul.e.luse@intel.com> Reviewed-by: <dongx.yi@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> |
||
|---|---|---|
| .. | ||
| accel | ||
| bdev | ||
| blob | ||
| blobfs | ||
| env_dpdk | ||
| event | ||
| sock | ||
| Makefile | ||