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>
20 lines
365 B
Plaintext
20 lines
365 B
Plaintext
{
|
|
global:
|
|
|
|
# Public functions
|
|
spdk_subsystem_find;
|
|
spdk_subsystem_get_first;
|
|
spdk_subsystem_get_next;
|
|
spdk_subsystem_get_first_depend;
|
|
spdk_subsystem_get_next_depend;
|
|
spdk_add_subsystem;
|
|
spdk_add_subsystem_depend;
|
|
spdk_subsystem_init;
|
|
spdk_subsystem_fini;
|
|
spdk_subsystem_init_next;
|
|
spdk_subsystem_fini_next;
|
|
spdk_subsystem_config_json;
|
|
|
|
local: *;
|
|
};
|