ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc/bdev: fix minor typo and format issues

Browse Source 
Change-Id: Iafee71dcdf8469a6c2edab42f4fc8e2f1778bef2
Signed-off-by: Chen Zhenghua <chen.zhenghua@zte.com.cn>
Reviewed-on: https://review.gerrithub.io/422247
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
Chen Zhenghua 2018-08-14 17:39:58 +08:00 committed by Jim Harris
parent 3f6f569854
commit 92ebb7c899
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/bdev_pg.md
View File

@ -56,7 +56,7 @@ spdk_allocate_thread().
From an allocated thread, the bdev library may be initialized by calling From an allocated thread, the bdev library may be initialized by calling
spdk_bdev_initialize(), which is an asynchronous operation. Until the completion spdk_bdev_initialize(), which is an asynchronous operation. Until the completion
callback is called, no other bdev library functions may be invoked. Similarly, callback is called, no other bdev library functions may be invoked. Similarly,
to tear down the bdev library, call spdk_bdev_finish. to tear down the bdev library, call spdk_bdev_finish().
## Discovering Block Devices ## Discovering Block Devices
@ -105,7 +105,7 @@ Once a descriptor and a channel have been obtained, I/O may be sent by calling
the various I/O submission functions such as spdk_bdev_read(). These calls each the various I/O submission functions such as spdk_bdev_read(). These calls each
take a callback as an argument which will be called some time later with a take a callback as an argument which will be called some time later with a
handle to an spdk_bdev_io object. In response to that completion, the user handle to an spdk_bdev_io object. In response to that completion, the user
must call spdk_free_bdev_io() to release the resources. Within this callback, must call spdk_bdev_free_io() to release the resources. Within this callback,
the user may also use the functions spdk_bdev_io_get_nvme_status() and the user may also use the functions spdk_bdev_io_get_nvme_status() and
spdk_bdev_io_get_scsi_status() to obtain error information in the format of spdk_bdev_io_get_scsi_status() to obtain error information in the format of
their choosing. their choosing.