Ok. My assumption is that it is preferred to be a single mode, but that
dual mode should be supported. Please note that dual mode may impact some
of the feature set in the emulated target - and it'll be a trick to identify
that.
Hmm... what this leads me to is - there is a difference between the
pure SCSI behavior (performing a SCSI Read command), and the transport-level
SCSI behavior (Mode Pages; FCP: Conf, Recovery; iSCSI CmdSN/StatSN progression,
SNACK, RSP retransmission, etc). Although, these will be very tightly
integrated. How does this code account for this ? Are there transport-level
libraries in-between the LLDD and the SCSI Target ? Is it reflected in the
LLDD to SCSI Target messaging ?
-- james
Mike Christie wrote:
James Smart wrote:
One question....
Does this assume that an hba is both initiator and target ? target only ?
Do we have any issues if a scsi_host is a target only ?
I do not think that is fully worked out yet. The only target that is
done is the vscsi one which is a little different from something like
lpfc or qla*. I think some developers like Qlogic would prefer the
driver and card is only in one mode or the other to simplify things.
However, I think Tomo and users would like to be able to use a
card/driver in both modes at the same time.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
