6368d6c0f5
With this new API, callers can attach one specific ctrlr identified by
the transport ID directly along with optional ctrlr opts. If connecting
to multiple controllers, it is still suggested to use spdk_nvme_probe()
and filter the requested controllers with the probe callback.
Two primary use cases:
1) connecting to the NVMe-oF discovery controller
2) more straightforward way to connect a specific controller (avoiding
the probe callback)
A typical usage of this API with specific ctrlr_opts:
1. struct spdk_nvme_ctrlr_opts user_opts = {}
2. Call spdk_nvme_ctrlr_get_default_ctrlr_opts(&user_opts, sizeof(user_opts))
3. Modify the content of the initialized user_opts with user required value like
user_opts.num_io_queues = 8
4. Call spdk_nvme_connect(&trid, &user_opts, sizeof(user_opts))
Change-Id: Idf67ee5966f6753918c12604342c892d2f3bbe3a
Signed-off-by: GangCao <gang.cao@intel.com>
Reviewed-on: https://review.gerrithub.io/370634
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
|
||
|---|---|---|
| .. | ||
| Makefile | ||
| nvme_ctrlr_cmd.c | ||
| nvme_ctrlr.c | ||
| nvme_internal.h | ||
| nvme_ns_cmd.c | ||
| nvme_ns.c | ||
| nvme_pcie.c | ||
| nvme_qpair.c | ||
| nvme_quirks.c | ||
| nvme_rdma.c | ||
| nvme_transport.c | ||
| nvme_uevent.c | ||
| nvme_uevent.h | ||
| nvme.c | ||