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

doc/iscsi: Remove obsolete limitation of the hotplug feature

Browse Source 
iSCSI hotplug should be pretty stable now.

Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Change-Id: Ie1a4fc167f75f4a1c9f079e53a78552f8ca9714d
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3493
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: John Kariuki <John.K.Kariuki@intel.com>
Reviewed-by: Paul Luse <paul.e.luse@intel.com>
This commit is contained in:
Shuhei Matsumoto 2020-07-23 09:40:41 +09:00 committed by Tomasz Zawadzki
parent 4ea197883c
commit d40a1b7eff
1 changed files with 0 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/iscsi.md
View File

@ -324,11 +324,4 @@ At the iSCSI level, we provide the following support for Hotplug:
wait for all the commands which have already been submitted to block device to wait for all the commands which have already been submitted to block device to
return back; after all the commands return back, the LUN will be deleted. return back; after all the commands return back, the LUN will be deleted.
## Known bugs and limitations {#iscsi_hotplug_bugs}
For write command, if you want to test hotplug with write command which will
cause r2t, for example 1M size IO, it will crash the iscsi tgt.
For read command, if you want to test hotplug with large read IO, for example 1M
size IO, it will probably crash the iscsi tgt.
@sa spdk_nvme_probe @sa spdk_nvme_probe