d086d56415
We want to be able to save the discovery configuration in a generated JSON-RPC file. The obvious change needed here is to add a bdev_nvme_start_discovery RPC to the config file for each discovery context. But we also need to make sure we do not emit bdev_nvme_attach_controller RPCs for controllers that were attached via the discovery service. These controllers will be attached by the discovery service instead - or maybe not at all if the discovery log page returns different results. Do both of these changes here, since they are somewhat tied to each other. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ic2072150c3efdd0a8d01da09e33a647e4929779b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11818 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> |
||
|---|---|---|
| .. | ||
| bdev_nvme_cuse_rpc.c | ||
| bdev_nvme_rpc.c | ||
| bdev_nvme.c | ||
| bdev_nvme.h | ||
| Makefile | ||
| nvme_rpc.c | ||
| vbdev_opal_rpc.c | ||
| vbdev_opal.c | ||
| vbdev_opal.h | ||