PDU with F bit set when ExpectedDataTransferLength larger than Max Burst Size

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Wanted you to clarify the expected behavior of LIO when a command (Read10) is issued with ExpectedDataTransferLength larger than Max Burst Size. What i see is that, in the response Data-In PDUs the F bit is getting set in PDU which is not the last Data-In PDU.
All other aspects seem to be fine the Data-sn is incrementing properly.
But i see multiple Data-in PDUs with F bit set getting received.
But RFC states F bit to be set in the Final Data-in PDU only.

FYI,
I am issuing a READ10 command with  the following

ExpectedDataTransferLength = 5120,6144 and 8192. I am observing the same behavior in all cases.

other parameters negotiated

MaxRecvDataSegmentLength=512
MaxBurstLength=4096
ImmediateData=No
MaxOutstandingR2T=1
DataSequenceInOrder=Yes
InitialR2T=Yes
DataPDUInOrder=Yes
DefaultTime2Retain=20


The LIO target details are as follows:

kernel : 3.10.13-101.fc18.x86_64 #1 SMP(Fedora 18)
rpm -qa | grep target
scsi-target-utils-1.0.38-1.fc18.x86_64
selinux-policy-targeted-3.11.1-66.fc18.noarch
targetcli-2.1.fb30-1.fc18.noarch


Regards,
Santosh
Senior Development Engineer
Calsoft Inc.
--
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




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux