Spdk/iscsi at a76cc7ce6192df58f4bba235ed485036b5d4f9c0 - Spdk

History

Pawel Wodkowski a76cc7ce61 bdev/iscsi: add create callback Also convert bdev_iscsi_set_module_init() into new callback. Change-Id: I439369180e1e10eab5dee6aba27ffb0489ea2550 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/410095 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>		2018-06-05 17:52:06 +00:00
..
bdev_iscsi.c	bdev/iscsi: add create callback	2018-06-05 17:52:06 +00:00
Makefile	bdev: add iSCSI initiator bdev module	2018-03-21 20:35:42 -04:00
README	bdev: add iSCSI initiator bdev module	2018-03-21 20:35:42 -04:00

README

This is a very rough initial cut at an SPDK iSCSI initiator bdev module.  It
only performs operations (connect, login, read cap, read/write).
But this passes basic verify tests with bdevperf and with fio.

Configuration file for iSCSI initiator is in the following format.
Note that the "/0" at the end means "LUN 0".

[iSCSI_Initiator]
  URL iscsi://127.0.0.1/iqn.2016-06.io.spdk:disk1/0 iSCSI0

To Do Items
===========
1) Create RPCs.
2) Use asynchronous polling for connect/login/disconnect.  Read/write is already
   using libiscsi event framework.
3) Choose initiator name as part of RPC configuration.  Currently this is hardcoded
   with g_initiator string.
4) Implement reset path.
5) Implement unmap path.
6) Use REPORT_LUNS to dynamically find all of the block devices attached to the
   iSCSI target node instead of hard-coding LUN 0.  This will need some extra
   investigation in libiscsi.  Currently the full URL is used which includes the LUN.
   Not sure yet how we can login to target node and then submit IO to different
   LUNs.  Let's treat this as low priority for now.