Commit d40a1b7e authored by Shuhei Matsumoto's avatar Shuhei Matsumoto Committed by Tomasz Zawadzki
Browse files

doc/iscsi: Remove obsolete limitation of the hotplug feature 



iSCSI hotplug should be pretty stable now.

Signed-off-by: default avatarShuhei 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: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarChangpeng Liu <changpeng.liu@intel.com>
Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
Reviewed-by: default avatarJohn Kariuki <John.K.Kariuki@intel.com>
Reviewed-by: default avatarPaul Luse <paul.e.luse@intel.com>
parent 4ea19788

doc/iscsi.md

+0 −7
Original line number Diff line number Diff line
@@ -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

  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