Folks, In particular we are not determining if multiple packets lost in a row are part of the same loss event.
This is evidenced in my test environment where we have machines about 1.5 msec apart (separated by a Linux router) and when running iperf we lose 100 packets (which is another problem but not sure what is causing it...). We get a loss interval for every single loss so we quickly get an i_mean of 1 (or p of 1000000) which is not good. The function that needs to be fixed is ccid3_hc_rx_detect_loss. This code is a little nasty. Just notifying the list for the record. I may or may not fix this but it won't be this week. Ian -- Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
