On Wed, 2013-11-13 at 11:16 +0530, Arshad Hussain wrote: > Hi Nicholas, > > On 11/13/2013 2:58 AM, Nicholas A. Bellinger wrote: > > Hi Arshad, > > > > On Tue, 2013-11-12 at 10:13 +0530, Arshad Hussain wrote: > >> Hi, > >> > >> We are doing a conformance test against a LIO based target. > >> > >> I am attempting a login, and I am not transmitting > >> "MaxRecvDataSegmentLength" key. > > IIRC, the target ends up sending it's own MRDSL key if the initiator > > never sends one. > Yes it is doing that. > > > >> I am passing through login phase and going into FFP. After this I am > >> sending a > >> text request with F = 0 and "MaxRecvDataSegmentLength=512" key. > >> > >> Once, I send the text request I am getting error under dmesg > >> "[877905.526656] Received Text Data that is not SendTargets, cannot > >> continue." > >> > >> When I am sending text request of "SendTargets=All" it is working. That > >> is, I am getting > >> the key/value for initiator and target. > > FYI that in >= v3.11 code, the other incarnations of SendTargets support > > have been added. > > > >> However, text request other than "SendTargets=" seems not to work. I > >> could also see that the target is not > >> responding with "not understood" etc... "MaxRecvDataSegmentLength=512" > >> key is simply ignored. > >> > >> Is this the correct behavior we are looking at, for text request as far > >> as LIO is concerned. ? > >> > > Correct, setting MRDSL within FFP using a Text command is not supported. > > Ok. I see. Will LIO keep it like this or in future you are planning to > add this feature? > Considering that no initiators that I'm aware of support changing MRDSL on the fly in FFP, and given the amount of logic involved to ensure synchronization (on both sides) when changing MRDSL with active I/O, the likelihood of supporting this without a mainstream initiator needing it is very low. --nab -- 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
