Ziye Yang 6134d778d4 conf: Transport should be explictly configured in conf file ... 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>		2018-11-15 04:49:08 +00:00
..
rpc	rpc: Add state_mask to each RPC method to make sets of RPCs	2018-05-03 19:48:15 +00:00
subsystems	conf: Transport should be explictly configured in conf file	2018-11-15 04:49:08 +00:00
app.c	app: RPC to wait for app subsystem initialization.	2018-11-12 22:21:33 +00:00
Makefile	build: remove $(ENV_CFLAGS) where not necessary	2018-01-03 12:05:59 -05:00
reactor.c	thread: Make the thread internally manage pollers	2018-11-13 14:26:37 +00:00
rpc.c	thread: Replace #include of io_channel.h with thread.h	2018-06-12 15:24:07 +00:00
subsystem.c	event: allow subsystem to write configuration in async way	2018-03-27 02:57:28 -04:00