Hi ,
I had a query.
Does LIO support DataSn Sequencing in DataOut PDUs(run of DataOuts for a
Single Write) ?
As far as the RFC goes its states DataSn is identified by either the ITT
or the R2T sequencing.
RFC
"For output (write) data PDUs, the DataSN is the Data-Out PDU number
within the current output sequence. The current output sequence is
either identified by the Initiator Task Tag (for unsolicited data) or
is a data sequence generated for one R2T (for data solicited through
R2T)."
Dmesg OutPut:
[11597.736859] Command ITT: 0xa3a3a3a3, received DataSN: 0x00000001
higher than expected 0x00000000.
[11600.744834] Dumping DataOUT PDU Offset: 1024 Length: 512 DataSN:
0x00000002
[11603.752879] Dumping DataOUT PDU Offset: 1536 Length: 512 DataSN:
0x00000003
[11606.760880] Dumping DataOUT PDU Offset: 2048 Length: 512 DataSN:
0x00000004
So basically i am issuing a Write10 PDU with size 3072 and responding
with Multiple DataOuts of sizes 512 bytes each(for every R2T i receive
from the target).
So when i use DataSn sequencing (using R2TSns) the above Dmesg is thrown.
It works fine for DataOut PDU run with DataSN set to 0x0 across all PDUs.
So does LIO support the Dataout PDU identification through just the ITT ?
Regards
Santosh
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
