af935f768e
This is useful for applications even if they elect not to use the SPDK event framework. This doesn't shift everything in one go - just the subsystem initialization logic. Configuration file loading also needs to move in a separate patch later. Change-Id: Id419df1045442d416650ed90e5ee78adfdd623d7 Signed-off-by: Ben Walker <benjamin.walker@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6641 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
|---|---|---|
| .. | ||
| nvme.libtest.mk | ||
| spdk_blank.map | ||
| spdk.app_cxx.mk | ||
| spdk.app_vars.mk | ||
| spdk.app.mk | ||
| spdk.common.mk | ||
| spdk.deps.mk | ||
| spdk.fio.mk | ||
| spdk.lib_deps.mk | ||
| spdk.lib.mk | ||
| spdk.mock.unittest.mk | ||
| spdk.modules.mk | ||
| spdk.nvmecli.mk | ||
| spdk.subdirs.mk | ||
| spdk.unittest.mk | ||