Thank you for this carefully worded bug report :-) Really, with the number of bugs that are still in the code, I am actually amazed that we get this far 8-) I don't think that doing performance-testing at this stage is of any use. When you repair your car and take out half of the engine, then take it for a spin, do you expect top-gear performance?
I don't really have time to respond properly at present. However I would say we shouldn't ever be making kernel worse and basically not working. My standard for submitting patches is that it still works at least as well as before. It's not good when users pull kernels and they don't work. It takes me (and anybody else) five minutes to test after each set of patches that I do. However it takes me hours/day to bisect faulty kernel trees.
Thank you for forwarding this onto the IETF list.
I am not sure if this is sarcasm or not. By forwarding to the IETF list I was trying to resolve a protocol (not implementation) issue of timers going off all the time - which unfortunately hasn't been answered yet. You're solving the problem in a good way but I wanted DCCP fixed (not your code). I'm sorry if I offended you - it wasn't my intent. -- 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html