The section of your README on interop with the Cisco
initiator is out of date.
The cmds_per_lun change is not needed. Recent Cisco
draft 8 and draft 19 Linux initiators use a depth of 1
for devices that don't support tagged command queueing,
such are your target.
I don't believe the ISCSI_USE_PHASE_COLLAPSED_READ_DFLT
change is needed. If you are aware of any problems
returning status on Data PDUs to the Cisco initiator,
please log a bug.
The main interop problem with the Cisco initiator is
the hard-coded assumption in the Intel target that all
Data PDUs for a command will immediately follow the
Command PDU, with no intervening Nop-out, Task Mgmt, or
Command PDUs. I don't see anything in the iSCSI spec
that allows targets to make that assumption, and the
Cisco initiator may send you a PDU you're not prepared
to handle, causing the target to error out. I've
reopened the bug I logged on this a while back,
explaining why I think your target is not conforming to