4bcfef0021
RPC is core functionality for SPDK applications and should always be initialized last (after all subsystems have been initialized). So make RPC a first class citizen and integrate it with the app framework directly instead of making it an "optional" subsystem. Then we initializing it after all subsystems have completed initialization, and tear it down before tearing down subsystems. We can also do some other cleanup while here - for example, reactors are already started when spdk_rpc_initialize() is called, so remove the extra event that was added during initialization since this is no longer needed. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I4cc63586a6d55be68786629a2176c61a88979267 Reviewed-on: https://review.gerrithub.io/385914 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
|---|---|---|
| .. | ||
| env_spdk.cc | ||
| spdk.rocksdb.mk | ||