doc/nvmf_tracing: fix a typo

Signed-off-by: Rami Rosen <ramirose@gmail.com>
Change-Id: I2d5b64eebe8f65a036675b8d3fcd1df3e8c2444b
Reviewed-on: https://review.gerrithub.io/c/444895
Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
Rami Rosen 2019-02-15 16:50:15 +02:00 committed by Darek Stojaczyk
parent 7592a5fe81
commit d8cf37d015

View File

@ -143,7 +143,7 @@ Also send I/Os to the SPDK target application to generate events by previous per
./perf -q 128 -s 4096 -w randread -t 600 -r 'trtype:RDMA adrfam:IPv4 traddr:192.168.100.2 trsvcid:4420'
~~~
After the completion of perf exmaple, shut down spdk_trace_record by signal SIGINT (Ctrl + C).
After the completion of perf example, shut down spdk_trace_record by signal SIGINT (Ctrl + C).
To analyze the tracepoints output file from spdk_trace_record, simply run spdk_trace program by:
~~~{.sh}