ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

event/nvmf: allow running without [Transport] in the legacy cfg file

Browse Source 
While useful in NVMf target, this is really annoying
in the consolidated spdk target, where NVMe-oF doesn't
even have to be used. OCF tests currently use iscsi_tgt
just because spdk_tgt requires the additional [Transport]
section in the cfg file. Let's remove that requirement.

Change-Id: I418b47d62dcc06b9513f9f0496dc1e39b9d5a554
Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/450056
Reviewed-by: Vitaliy Mysak <vitaliy.mysak@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
Darek Stojaczyk 2019-04-03 17:18:08 +02:00 committed by Jim Harris
parent 1468f8dd3b
commit 728af01741
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
lib/event/subsystems/nvmf/conf.c
View File

@ -581,11 +581,7 @@ spdk_nvmf_parse_transports(spdk_nvmf_parse_conf_done_fn cb_fn)
/* if we get here, there are no transports defined in conf file */
free(ctx);
SPDK_ERRLOG("\nNo valid transport is defined yet.\n"
"When using configuration file, at least one valid transport must be defined.\n"
"You can refer the [Transport] section in spdk/etc/spdk/nvmf.conf.in as an example.\n");
cb_fn(-1);
cb_fn(0);
return 0;
}