Re: [BUG] CCID3 - loss not detected if in order
Hi Ian, I had been trying to get a p value other than zero from some days, and I was relieved when I read your post yesterday. So I applied your lossfix and ccid3li patches (and all the other patches in http://wand.net.nz/~iam4/dccp/patches/ actually) to my linux boxes (both senderreceiver) and started some testing. However, the linux box at the receiver side (scenario: sending data from sender to receiver) got freezed everytime I played the scenario and I had to switch off/on the machine to get it back to life. There seems to be a problem related with the patches I applied, maybe txbuff patch. Do you have any idea? Burak Gorkemli Ph.D. Candidate Koc University Turkey - 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
[BUG] CCID3 - loss not detected if in order
Hi folks, Loss is not being detected correctly in CCID3 and p never gets to be anything but 0. In ccid3_hc_rx_packet_recv the loss code can only be called if dccp_rx_hist_add_packet returns 1. This only can only return 1 if packets are out of order. In normal loss this will never return 1. p therefore does not get set to anything but 0. This causes CCID3 to send packets too fast which explains some of the behaviour I'm seeing. I am thinking about how to fix this at the moment but as always others are free to dive in! Ian -- Ian McDonald Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group Department of Computer Science University of Waikato New Zealand - 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
