On Tue, Dec 1, 2009 at 3:16 PM, Ulrich Windl <ulrich.wi...@rz.uni-regensburg.de> wrote: > On 1 Dec 2009 at 14:57, Erez Zilber wrote: > >> Maintain a list of nop-out PDUs that almost timed out. >> With this information, you can understand and debug the >> whole system: you can check your target and see what caused >> it to be so slow on that specific time, you can see if your >> network was very busy during that time etc. >> > > Hi! > > Having studied TCP overload protection and flow control mechanisms recently, I > wondered if a look at the TCP window sizes could be a indicator equivalent to > timed-out nops. My idea is: Why implement something, if it's possibly already > there for free. > > Regards, > Ulrich >
We've discussed and agreed on the idea of a list of nop-out PDUs that almost timed out (http://groups.google.com/group/open-iscsi/msg/02b93de35e80697c) and here's the patch. I'm not familiar enough with the mechanism that you describe, but the patch that I sent does the job with an easy to use iscsiadm interface. Erez -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
