update source to Ceph Pacific 16.2.2

[ceph.git] / ceph / src / spdk / doc / applications.md

diff --git a/ceph/src/spdk/doc/applications.md b/ceph/src/spdk/doc/applications.md
index cb360c7f1c9224eacb9ecdbeb8e51d999302aa5c..f841b1c84e9e96d4dcf5ce1aa2418af5478f2b69 100644 (file)
--- a/ceph/src/spdk/doc/applications.md
+++ b/ceph/src/spdk/doc/applications.md
@@ -47,7 +47,6 @@ Param    | Long Param             | Type     | Default                | Descript
 |        | --huge-dir             | string   | the first discovered   | allocate hugepages from a specific mount
 -L       | --logflag              | string   |                        | @ref cmd_arg_debug_log_flags
 
-
 ### Configuration file {#cmd_arg_config_file}
 
 Historically, the SPDK applications were configured using a configuration file.
@@ -76,12 +75,12 @@ SPDK applications progress through a set of states beginning with `STARTUP` and
 ending with `RUNTIME`.
 
 If the `--wait-for-rpc` parameter is provided SPDK will pause just before starting
-subsystem initialization. This state is called `STARTUP`. The JSON RPC server is
-ready but only a small subsystem of commands are available to set up initialization
+framework initialization. This state is called `STARTUP`. The JSON RPC server is
+ready but only a small subset of commands are available to set up initialization
 parameters. Those parameters can't be changed after the SPDK application enters
 `RUNTIME` state. When the client finishes configuring the SPDK subsystems it
-needs to issue the @ref rpc_start_subsystem_init RPC command to begin the
-initialization process. After `rpc_start_subsystem_init` returns `true` SPDK
+needs to issue the @ref rpc_framework_start_init RPC command to begin the
+initialization process. After `rpc_framework_start_init` returns `true` SPDK
 will enter the `RUNTIME` state and the list of available commands becomes much
 larger.