6134d778d4
According to the currrent logic, it should be explictly defined in the configuration file if the NVMe-oF target is started by configuration file without using rpc calls. If no transport is defined, we do not need to parse the following subsystems but should terminate the NVMe-oF target . Change-Id: I2e2db8406a30a9bf7e54d38f8d08a8d92ef158c9 Signed-off-by: Ziye Yang <optimistyzy@gmail.com> Reviewed-on: https://review.gerrithub.io/432376 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
---|---|---|
.. | ||
iscsi.conf.in | ||
nvmf.conf.in | ||
vhost.conf.in |