Commit d5da6912 authored by Krzysztof Karas's avatar Krzysztof Karas Committed by Tomasz Zawadzki
Browse files

doc: Mention spdk_top in `Getting Started`. 



Change-Id: I708483b9b22ca7f050e9088d6f9dff313fb87822
Signed-off-by: default avatarKrzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/18456


Reviewed-by: default avatarShuhei Matsumoto <smatsumoto@nvidia.com>
Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarBen Walker <benjamin.walker@intel.com>
parent 522abe47

doc/getting_started.md

+5 −1
Original line number Diff line number Diff line
@@ -112,4 +112,8 @@ A good example to start with is `build/examples/identify`, which prints 
out information about all of the NVMe devices on your system.



Larger, more fully functional applications are available in the `app`

directory. This includes the iSCSI and NVMe-oF target.
 
directory. This includes the [iSCSI target](https://spdk.io/doc/iscsi.html)

and [NVMe-oF target](https://spdk.io/doc/nvmf.html) and tools like

[spdk_top](https://spdk.io/doc/spdk_top.html). This neat program simulates

regular `top` application and shows SPDK threads, pollers and SPDK assigned

CPU cores statistics in a form of interactive list.