On Tue, 2014-05-27 at 10:52 +0530, Arshad Hussain wrote: > Hi Nab, > > Thanks for the explanation. Yes the initiator is throwing incorrect > TTT. Should not this be handled by the Target?. If this is the valid > error, then I would be happy to provide in the patch. > It's not a error because the initiator sending ITT=<some value> + TTT=0xffffffff is a valid NOP-OUT request soliciting a NOP-IN response from the target. > Couple of question regarding NOP-In to help me understand the behavior > better. (a) When does target (LIO) decide to send out unsolicited NOP-In > assuming there will be corresponding NOP-Out (Valid TTT). A NOP-IN with a valid ITT=0xffffffff + TTT=<some value> is generated on a per connection basis every 'nopin_timeout' seconds. > (b) When target send sout NOP-In without wanting to receive a > corresponding NOP-Out.? > Never. If no NOP-OUT with a TTT matching the solicited NOPIN TTT is received after 'nopin_response_timeout' seconds, the connection will be forced into reinstatement. --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
