Quoting Ian McDonald: | > I think that a warning message could bring in some light: maybe it is the case here that the RTT measurement is just | > at rock bottom, always returns 0, and thus always stays at 1. | | It was just put in there to stop divide by zeros. It wasn't meant to | be a proper fix. I have added warning messages in latest patch. | > | > There is another thread which I think may be of relevance, incidentally again at the rx_packet_recv function: | > | > http://www.mail-archive.com/dccp%40vger.kernel.org/msg00118.html | > | This one has already been fixed. If you look at the code it's changed | a fair bit since then. This was a bug which crippled my testing and I | was glad to get sorted. I also removed some of the cc_val/window stuff | at this point as I figured 80% working was better than 0% working as | regards to congestion control... I take your word for it - when looking yesterday, I noted that new functions and variable names were used, but the structure seemed somewhat similar - but I am not so familiar with the CCID 3 code. Will do some more code reading. -- Gerrit - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
