Many thanks indeed for the input - referred to in the other email as well. | So my primary suggstion is to accept that there is a limit to | how accurate you can get timestamps, there is also a specific | regime under which fine-RTT measurements matter, and therefore | the algorithm chosen has to match that reality. | I think that by building on such realities we stand a better chance of arriving at a workable solution than by blindly trying to cast a specification into code. There is some revision to be done where your input is very helpful. I hope that Eddie will incorporate/pick up the point to bypass the congestion control when RTTs are low. Ian and Eddie seem to have differing opinions regarding RTT accuracy and I think I also need to check. ( If only we could use jiffie-based algorithm, that would axe the cost of all these gettimeofdays (they still exist, even after retracting the skb_get_timestamp patches). There is this really nice TCP algorithm which doesn't use timestamps, tcp_rcv_rtt_update() in tcp_input.c . ) - 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
