Mike, After looking into the iSCSI spec again, I realized that target can't reduce the MaxCmdSN after the login has occurred.
The iscsi_update_cmdsn() is fine. It is doing exactly what it is suppose to do. I guess, if the target does have to reduce the windows size, it can send an asynchronous logout and give a reduced window size when the initiator log back in. This will work fine with the patch that you provided. Thx, Arvind. -----Original Message----- From: firstname.lastname@example.org [mailto:[EMAIL PROTECTED] On Behalf Of Mike Christie Sent: Friday, June 27, 2008 4:32 PM To: email@example.com Subject: Re: MaxCmdSN not set after auto login Arvind Jain wrote: > Mike, > Thanks for the patch. I came to the same conclusion after looking into the > function iscsi_update_cmdsn(). > Perhaps, you could do the same thing for hdr->opcode == ISCSI_OP_NOOP_IN. > This will allow the target to dynamically adjust the window size in case of > a resource constraint when running multi-initiators. > Thx, Arvind. > So what are you guys actually sending in this case? The cmdsn definitions in 126.96.36.199 define what targets can do and how are supposed to process the values, but I am not sure what you guys are sending and how to then handle it wrt to the spec. Is iscsi_update_cmdsn busted or are you sending something weird? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to firstname.lastname@example.org To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---