When user used CUSTOM transport, follow this step can reproduce: 1. run ./nvmf_tgt 2. ./rpc.py nvmf_create_transport -t ABC (ABC is the transport name) 3. ./rpc.py save_config >> config.json Then in config.json : { "subsystem": "nvmf", ... "config": [ { "method": "nvmf_create_transport", "params": { "trtype": "CUSTOM", ... } ] } trtype should be ABC , because nvmf_create_transport need pass the transport name to create transport. Signed-off-by: jiaqizho <jiaqi.zhou@intel.com> Change-Id: Iaf24837b649a1736568902f898d48135dac0882d Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4973 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jacek Kalwas <jacek.kalwas@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> |
||
---|---|---|
.. | ||
ctrlr_bdev.c | ||
ctrlr_discovery.c | ||
ctrlr.c | ||
fc_ls.c | ||
fc.c | ||
Makefile | ||
nvmf_fc.h | ||
nvmf_internal.h | ||
nvmf_rpc.c | ||
nvmf.c | ||
rdma.c | ||
spdk_nvmf.map | ||
subsystem.c | ||
tcp.c | ||
transport.c | ||
transport.h |